NASA-AMMOS / NASA-AMMOS/plandev-sequence-languages
Set up release action to appropriately flag prereleases
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
npm publish has a --tag next mode that you can pass so that dev/alpha/otherwise non-release versions don't get picked up on NPM as official releases. We should set up the release action to detect a non-release version tag and tell NPM, because right now our alpha releases show up as the latest on NPM.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository's release action and its npm publish invocation; review how version tags are passed to the package publication step. Done means non-release versions publish with npm's next tag while official versions remain latest, with the action workflow checked for both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100