Skip to content

release: autter 3.10.1 — publish the npm package with trusted publishing - #106

Merged
sagnik11 merged 3 commits into
mainfrom
ci/npm-trusted-publishing
Nov 15, 2026
Merged

sagnik11 merged 3 commits into
mainfrom
ci/npm-trusted-publishing

Conversation

@sagnik11

@sagnik11 sagnik11 commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

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 the NPM_TOKEN secret. @autter/cli on 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-npm job in release.yml now uses npm trusted publishing (OIDC). A trusted publisher is set up on npmjs.com for @autter/cli: GitHub Actions, Autter-dev/autter-cli, workflow release.yml, npm publish allowed.

  • runs-on: ubuntu-latest: npm accepts GitHub-hosted runners only, not Blacksmith.
  • Job-level permissions: { contents: read, id-token: write }.
  • Node 24 and npm install -g npm@11: trusted publishing needs npm 11.5.1 or newer.
  • No NODE_AUTH_TOKEN or registry-url, and the "skip when NPM_TOKEN is unset" check is gone; it would skip every publish once the secret is removed.
  • Skips on a re-run when the version is already on npm.

The second commit bumps the version to 3.10.1 (CLI unchanged from 3.10.0), so merging this tags v3.10.1 and 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

  • Confirm npm view @autter/cli dist-tags shows latest: 3.10.1.
  • Then set the package's publishing access to "Require two-factor authentication and disallow bypass 2fa tokens", and delete the NPM_TOKEN secret from this repo.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

sagnik11 and others added 2 commits November 15, 2026 14:55
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>
@blacksmith-sh

This comment has been minimized.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sagnik11
sagnik11 merged commit ae6fb53 into main Nov 15, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant