Repository navigation
release: autter 3.10.1 — publish the npm package with trusted publishing - #106
Merged
Merged
Conversation
The npm publish job authenticated with an NPM_TOKEN repo secret, and npm rejected it for 3.10.0 (404 on PUT), so @autter/cli stayed at 3.9.3 while the GitHub release went out. npm caps publish tokens' lifetime, so this would keep recurring. The job now authenticates with npm trusted publishing (OIDC): npmjs.com trusts Autter-dev/autter-cli's release.yml, so there is no token to expire. It runs on ubuntu-latest (npm accepts GitHub-hosted runners only), requests id-token: write, uses Node 24 with npm 11, and skips on a re-run when the version is already on npm. The old skip-when-no-token check is gone; it would have skipped every publish once the secret is removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
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.
Why
3.10.0's GitHub release went out, but its npm publish failed twice with
404 Not Found - PUT https://registry.npmjs.org/@autter%2fcli: npm no longer accepted theNPM_TOKENsecret.@autter/clion npm is still 3.9.3. npm caps how long publish tokens last, so renewing the token would only postpone the next failure.What changes
The
publish-npmjob inrelease.ymlnow uses npm trusted publishing (OIDC). A trusted publisher is set up on npmjs.com for@autter/cli: GitHub Actions,Autter-dev/autter-cli, workflowrelease.yml,npm publishallowed.runs-on: ubuntu-latest: npm accepts GitHub-hosted runners only, not Blacksmith.permissions: { contents: read, id-token: write }.npm install -g npm@11: trusted publishing needs npm 11.5.1 or newer.NODE_AUTH_TOKENorregistry-url, and the "skip whenNPM_TOKENis unset" check is gone; it would skip every publish once the secret is removed.The second commit bumps the version to 3.10.1 (CLI unchanged from 3.10.0), so merging this tags
v3.10.1and runs the release. That publish has to happen within 2 days of the trusted publisher being created, or npm drops the connection.After this merges
npm view @autter/cli dist-tagsshowslatest: 3.10.1.NPM_TOKENsecret from this repo.🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.