ci: modernize release pipeline + bump to 0.1.5 - #2
Merged
Conversation
Drops the NPM_TOKEN secret in favor of npm's trusted publisher flow, which authenticates the runner via GitHub Actions OIDC. Adds id-token: write to the release job, upgrades npm to a version that supports trusted publishing, and enables --provenance so published artifacts carry a verifiable build attestation. Requires a one-time trusted publisher config on npmjs.com for @bobbin/cli pointing at jtnkminimal/bobbin-cli + release.yml. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <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
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.
Summary
actions/checkoutandactions/setup-nodefrom v4 to v5 across all workflows. v4 runs Node.js 20 which GitHub deprecates June 2, 2026.npm publishfromNPM_TOKENto trusted publishing (OIDC). Trusted publisher is already configured on npmjs.com for@bobbin/clipointing at this repo +release.yml.--provenanceso published artifacts carry a verifiable build attestation.0.1.4→0.1.5(skips0.1.4because that tag was burned by the failed publish attempt).Why one PR
Merging in isolation would either leave a stale
NPM_TOKENreference (token PR before action bumps) or break tag releases (action bumps before token PR has been validated). Bundled, the next tag push exercises both end-to-end.Test plan
node dist/cli.js --version→0.1.5)v0.1.5→ release job publishes to npm via OIDC, no secret involvednpm view @bobbin/cli versionreturns0.1.5npm view @bobbin/clishowsprovenance: signed🤖 Generated with Claude Code