Repository navigation
ci: publish npm packages on v* tags with trusted publishing - #11
Merged
Merged
Conversation
A v* tag builds, tests and publishes @heightproof/shared, sdk-node and web3 in dependency order. Authentication is npm trusted publishing (OIDC), so no npm token is stored in GitHub, and every release carries provenance. The workflow refuses a tag that does not match every package version or an exact internal pin, skips versions already on npm so a failed run can be re-run, and can be dry-run from the Actions tab. RELEASING.md covers cutting a release and the one-time setup: the first publish by hand, then adding the trusted publisher on npmjs.com. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What
A
v*tag now publishes@heightproof/shared,@heightproof/sdk-nodeand@heightproof/web3to npm in dependency order, alongside the images and Helm chart thatrelease.ymlalready publishes.id-token: write.@heightproof/*pin between packages, differs from the tagdry_run(on by default).RELEASING.mddocuments cutting a release and the one-time setup. npm only allows a trusted publisher on a package that already exists, so the first0.1.0publish is done by hand.Testing
v0.1.0v0.2.0(version mismatch)DRY_RUN=true. All three packages pack in the right order.🤖 Generated with Claude Code