Publish to npm via OIDC in the release workflow#34
Merged
Conversation
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
1 participant
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.
Problem & Solution Overview
The release workflow ran the package smoke test but had no publish step. It now adds a
publishjob that runs after the smoke test and, on a version tag (refs/tags/v*), publishes to npm using OIDC trusted publishing — no long-lived token, provenance attached automatically. It upgrades npm to a trusted-publishing-capable version (>= 11.5.1) and setsid-token: write.Testing Done
release.ymlvalidated as YAML. Publish is gated to version tags and depends on the smoke job, so pushingv1.3.0runs smoke → publish.