chore: simplify publishing a test package#37
Merged
Conversation
Co-authored-by: Copilot <copilot@github.com>
michaeladams
approved these changes
Apr 27, 2026
|
🎉 This PR is included in version 3.1.2 🎉 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
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.
Since changes to make-it-so are generally made as part of changes to an app you often need some way to publish make-it-so changes so they can be used for testing with the app. Currently the process is to use the CI to publish pre-release versions to npm. But this is slow and clutters up the npm versions list. I recently came across https://www.npmjs.com/package/git-publish which is a much better fit for this situation.
Occasionally we need to test CI publishing (like if npm changes their auth requirements like they did recently) without actually making a proper release. So we keep that option to do prereleases via the CI but we simplify it to just work with the branch "ci-publish-test" rather than any branch starting with "internal-testing-".