Repository navigation
Stage npm releases for maintainer approval - #71
Merged
Merged
Conversation
ichernev
approved these changes
Nov 12, 2026
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
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.
Releases now go through npm's staged publishing: the release job only stages the version, and it goes live once a package maintainer approves it with 2FA, on npmjs.com or with
npm stage approve. With direct publishing, anyone who can create a GitHub release here can ship a new version of the SDK. npm recommends stage-only for trusted publishers.deploy.ymlrunsnpm stage publish, with verbose logging because npm logs trusted-publishing errors only at that level.NPM_TOKENfallback is removed. npm uses trusted publishing whenever it works, and that token, from 2024, is the one the 2.1.0 publish failed with.RELEASE.MDgets the approval step.Checked with npm 11.19.1, which Node 24 bundles:
npm stage publish --dry-runwith the workflow's flags stagesdeepinfra@2.2.0(155 files), andnpm stage publishgoes through the same trusted-publishing sign-in and provenance code asnpm publish.To finish the switch on npm, untick
npm publishon the trusted publisher before the release. Once a release has gone through, set the package's Publishing access to "Require two-factor authentication and disallow tokens".