Skip to content

ci: migrate npm publish to OIDC trusted publishing - #51

Merged
zipper merged 1 commit into
masterfrom
ci/oidc-trusted-publishing
May 14, 2026
Merged

zipper merged 1 commit into
masterfrom
ci/oidc-trusted-publishing

Conversation

@zipper

@zipper zipper commented May 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Migrace publish workflow z NPM_AUTH_TOKEN na npm trusted publishing přes OIDC.

Changes

  • 🛠️ publishPublic: přidán permissions: id-token: write + contents: read, odstraněn NODE_AUTH_TOKEN (NPM_AUTH_TOKEN), přidán --provenance flag
  • 🛠️ release: přidán permissions: contents: write, přejmenován na "GitHub Release"
  • 🛠️ Bump actions/checkout a actions/setup-node na v5
  • 🛠️ publishPrivate: jen bump actions (dál používá GITHUB_TOKEN)

Why

Stávající NPM_AUTH_TOKEN může expirovat (přesně to se stalo u pd-modal). OIDC trusted publishers nevyžadují žádný secret a poskytují provenance attestaci. Trusted publisher je už nastavený na npmjs.com.

Reference

Stejná migrace proběhla u peckadesign/pd-modal.

Test plan

  • CI checks projdou na PR
  • Po merge: vytvořit testovací tag, ověřit že publishPublic projde s --provenance a bez tokenu
  • Ověřit, že balíček na npmjs má provenance badge

- Switch to npm provenance via OIDC (no NPM_AUTH_TOKEN needed)
- Add id-token: write permission to publishPublic job
- Bump actions/checkout and actions/setup-node to v5
- Add contents: write permission to release job
@zipper
zipper merged commit 07b850e into master May 14, 2026
1 check passed
@zipper
zipper deleted the ci/oidc-trusted-publishing branch May 14, 2026 10: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.

1 participant