chore: prep 5.1.0-beta.1 release and tag prereleases as 'beta' on npm#115
Merged
Conversation
Bumps jvm/pom.xml to 5.1.0-beta.1 so the Maven artifact version matches npm/package.json. Updates PublishNPM.yml to detect pre-release versions (semver hyphen) and publish them under the 'beta' dist-tag, so beta releases no longer overwrite 'latest' on npm. Final releases continue to publish as 'latest'.
nawforce
approved these changes
May 16, 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.
Summary
jvm/pom.xmlfrom5.1.0-SNAPSHOTto5.1.0-beta.1so the Maven artifact version matchesnpm/package.jsonfor the upcoming beta release.PublishNPM.ymlto detect pre-release versions (semver hyphen) and publish them under thebetadist-tag. Final releases continue to publish aslatest.Why
The v5.0.0-beta.5 publish landed as
lateston npm because the workflow always rannpm publish --access publicwith no--tag. With this change, any version containing a-(e.g.5.1.0-beta.1,5.2.0-rc.1) publishes as@beta, leavinglatestpointing at the most recent stable release.Test plan
Buildworkflow) passes — pom version bump and a workflow file edit shouldn't affect build/test outputs.v5.1.0-beta.1, create a GitHub pre-release, then manually dispatchPublish to NPMandPublish to Maven.npm view @apexdevtools/apex-parser dist-tagsshowslatestunchanged andbetaset to5.1.0-beta.1.io.github.apex-dev-tools:apex-parser:5.1.0-beta.1.