Skip to content

ci: publish to npm via trusted publishing (OIDC) - #39

Merged
ivnbogdan merged 1 commit into
mainfrom
ci/npm-trusted-publishing
Oct 16, 2026
Merged

ivnbogdan merged 1 commit into
mainfrom
ci/npm-trusted-publishing

Conversation

@ivnbogdan

Copy link
Copy Markdown
Contributor

Summary

  • Switch the publish-npm release job from the NPM_TOKEN secret to npm trusted publishing (OIDC). The previous run (1.2.0) failed with ENEEDAUTH because the secret was never set.
  • Grant the job id-token: write (and contents: read).
  • Move to Node 24 and run npm install -g npm@latest, since trusted publishing needs npm >= 11.5.1 (Node 20 ships npm 10).
  • Provenance attestations are generated automatically.

The crates.io job is unchanged and still needs CARGO_REGISTRY_TOKEN (or a follow-up to use crates.io trusted publishing).

Prerequisite

Trusted publisher configured on npmjs.com for @aptabase/tauri: owner aptabase, repo tauri-plugin-aptabase, workflow release.yml, with Allow npm publish enabled.

Test plan

  • Next GitHub release: Publish to npm job succeeds and the new version shows a provenance badge on npmjs.com

🤖 Generated with Claude Code

Replace the NPM_TOKEN secret with npm trusted publishing: grant the job
id-token: write, move to Node 24 and upgrade npm to >= 11.5.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ivnbogdan
ivnbogdan merged commit ecfa1b7 into main Oct 16, 2026
1 check 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