Skip to content

fix(release): use npm trusted publishing - #18

Merged
routeplane-ops merged 1 commit into
mainfrom
ci/npm-trusted-publishing
Aug 13, 2026
Merged

fix(release): use npm trusted publishing#18
routeplane-ops merged 1 commit into
mainfrom
ci/npm-trusted-publishing

Conversation

@routeplane-ops

Copy link
Copy Markdown
Collaborator

The v0.5.0 publish run supplied NODE_AUTH_TOKEN, so pnpm chose the legacy automation token instead of the already-configured npm Trusted Publisher. npm correctly rejected that token under publish-time 2FA. No v0.5.0 package was published.

This change:

  • removes the long-lived npm credential and project .npmrc
  • isolates build/test/pack from the OIDC-enabled publish job
  • publishes only three same-run tarballs with lifecycle scripts disabled
  • binds tags to main and all three package versions
  • disables release caches and SHA-pins every action
  • advances the immutable retry to v0.5.1

Validation:

  • pnpm install --frozen-lockfile
  • pnpm build
  • pnpm test (121 tests)
  • pnpm lint
  • npm publish --dry-run for all three tarballs
  • actionlint
  • zizmor (no findings)
  • git diff --check
  • independent security review: SHIP

@routeplane-ops
routeplane-ops merged commit 10dc14f into main Aug 13, 2026
1 check passed
@routeplane-ops
routeplane-ops deleted the ci/npm-trusted-publishing branch August 13, 2026 17:23
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.

2 participants