ci(PP-3449): publish prereleases under npm beta dist-tag - #184
Merged
Conversation
Prerelease tags (e.g. v1.0.0-beta.1) now publish with --tag beta instead of the implicit latest, so a beta version never becomes the default install for existing consumers. Also add workflow_dispatch so a given tag can be re-published on demand without needing a new push event.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 task
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
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
v1.0.0-beta.1) now publish to npm with--tag betainstead of the implicitlatest, so a beta build never becomes the default install for existing consumers (npm installwithout a version, or anyone trackinglatest). Testers opt in explicitly vianpm install @metricinsights/pp-dev@beta.v1.0.0) are unaffected and still publish aslatest.workflow_dispatchso a specific tag can be manually re-run through this workflow later (e.g.gh workflow run release.yml --ref v1.0.0-beta.2), once this change has landed onmain.Notes
release-beta.yml/.releaserc.json(semantic-release) — that flow only bumps versions and creates git tags ondevelop, it does not publish to npm and pushes using the defaultGITHUB_TOKEN, which per GitHub Actions' own token-triggered-workflow suppression rule does not cascade into this workflow. This PR only affects the manual, tag-push-triggered production release flow.v0.20.0-beta.1/2/3) predate this change and are intentionally left alone — re-running them viaworkflow_dispatchwould execute the old release.yml as it existed at that commit (alwayslatest), not this fix.Testing
v1.0.0→latest,v1.0.0-beta.1→beta)Merge Request:
origin/pp-3449-npm-beta-tag→origin/develop