fix(release): only publish alpha and production releases to NPM#218
Merged
fix(release): only publish alpha and production releases to NPM#218
Conversation
chickenn00dle
approved these changes
Oct 16, 2025
|
🎉 This PR is included in version 5.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
All Submissions:
Changes proposed in this Pull Request:
Our release CI job will currently publish any tagged release to NPM. This results in pretty messy versioning on NPM. This PR updates the release job to only publish to NPM if the release is an alpha or production release, going forward.
How to test the changes in this Pull Request:
It won't be super easy to test this before it's merged and released to NPM itself, but after that, we can test by pushing a new
hotfix/*orepic/*branchname to Newspack Blocks and confirming that the resulting tagged prerelease is NOT published to NPM, but new alpha or release tags ARE published.Other information: