ci: automate npm publish on version tags via Trusted Publishing - #16
Draft
ScreamingHawk wants to merge 2 commits into
Draft
ci: automate npm publish on version tags via Trusted Publishing#16ScreamingHawk wants to merge 2 commits into
ScreamingHawk wants to merge 2 commits into
Conversation
Adds a release workflow that triggers on v* tags, verifies the tag matches package.json, builds, and publishes with npm Trusted Publishing (no NPM_TOKEN secret; provenance attached automatically). RELEASING.md documents the one-time npm-side trusted-publisher setup and the release procedure.
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
Adds automated deployment: pushing a
v*tag now publishes@0xsequence/codegenieto npm..github/workflows/release.yml— triggers on version tags; verifies the tag matchespackage.json, typechecks, builds, and runsnpm publishvia npm Trusted Publishing (OIDC). NoNPM_TOKENsecret; provenance attestations are attached automatically.RELEASING.md— documents the one-time npm-side setup and the release procedure.Blocked on npm-side setup
@pkieltyka — could you (or another package owner) add a Trusted Publisher on npmjs.com for
@0xsequence/codegenie?0xPolygon, Repository:codegenie, Workflow:release.yml, Environment: (empty)Until that's configured, the workflow will fail at the publish step (everything before it — version check, build — still runs, so a tag push can dry-run the rest).
Notes
actionlint/pnpm run check:workflowslocally.@0xsequencescope (per the README note), the trusted-publisher entry needs recreating on the new name.