Repository navigation
Automate validated npm releases with trusted publishing - #2
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Automate semantic versioning and public npm publication after the initial release.
Reuse the complete CI matrix as a prerequisite, create/update a Changesets version/changelog PR, explicitly dispatch CI for the generated branch, and publish merged release versions using npm OIDC with provenance. Pin Changesets Action, avoid a persistent npm token, skip published versions and obsolete queued commits, and document setup/recovery.
Validation: typecheck, build, package/bundler validation, and 72 clean-corpus unit tests passed locally. The publish dry run recognizes the existing 0.1.0 registry version and does not republish it. CI validates the browser matrix on a clean checkout.
External setup: npm must trust su-engineering/heic-web workflow release.yml with direct npm publish allowed; the organization must permit Actions-created PRs. No npm token secret is required.