ci: Route npm pre-releases to the 'beta' dist-tag#18
Merged
Conversation
Mirrors the auto-detection in apex-parser's PublishNPM.yml: if the version contains a '-' (semver pre-release), publish under `--tag beta` so `npm install @apexdevtools/vf-parser` keeps resolving to the latest stable rather than picking up `2.0.0-beta.1`. Stable versions still publish as `latest`.
nawforce
approved these changes
May 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports the version-aware dist-tag logic from
apex-parser/.github/workflows/PublishNPM.ymlso that publishing2.0.0-beta.1doesn't clobber the npmlatesttag.Behaviour
-(semver pre-release) →npm publish --access public --tag betanpm publish --access public(defaults tolatest)Means a future stable
2.0.0release needs no workflow change to flip back.Test plan
2.0.0-beta.1release — verify on npmjs.com thatlateststill points at1.xandbetapoints at2.0.0-beta.1after the publish workflow runs.