Rearrange GitHub Actions to allow publishing to NPM #1081
Merged
Conversation
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
also temporarily set the package.json version to 2.0.0-alpha1 so I don't accidentally clobber the 2.0.0 version while testing
EzraBrooks
commented
Nov 17, 2025
Collaborator
Author
There was a problem hiding this comment.
This PR is mostly just reorganizing things so I could create a dedicated workflow for Trusted Publishing to NPM so we don't need to use an NPM token secret.
Collaborator
Author
|
once this and the follow-up PR #1082 are in, I think we're good to cut a pre-release of 2.0. |
bjsowa
approved these changes
Nov 17, 2025
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.
also temporarily set the package.json version to 2.0.0-alpha1 so I don't accidentally clobber the 2.0.0 version while testing