Automated npm releases from main - #18
Merged
Merged
Conversation
Release workflow: on every push to main, compare package.json version with the npm registry and publish when it is new. Publishing uses npm trusted publishing (OIDC), so no token secret, and provenance comes with it. prepublishOnly still gates every publish behind typecheck, tests, and build. Closes the provenance item on #11.
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.
On every push to main the workflow compares the package.json version against the npm registry and publishes when it is new. Release ritual becomes: bump the version, merge to main.
prepublishOnlystill gates every publish behind typecheck, tests, and buildOne-time setup needed before this works (npm side, about a minute):
2fa-kit-> Settings -> Trusted Publisheramansoomro062/2fa-kitand workflowrelease.ymlUntil that is configured, a version-bump push will fail the publish step with an auth error, nothing worse.