ci(publish): clear npm tokens for trusted publishing#198
Merged
Abhijeet Prasad (AbhiPrasad) merged 1 commit intoJun 9, 2026
Merged
Conversation
Clear NODE_AUTH_TOKEN and NPM_TOKEN on the npm publish steps so npm uses GitHub OIDC trusted publishing instead of an injected token from setup-node. The failed autoevals@0.3.0 release had a NODE_AUTH_TOKEN present during npm publish, which caused npm to attempt token-based publishing and return a misleading 404 for the package. This mirrors the working publish setup in braintrust-sdk-javascript while preserving provenance publishing for both stable and prerelease releases.
Braintrust eval report
|
Caitlin Pinn (cpinn)
approved these changes
Jun 9, 2026
Abhijeet Prasad (AbhiPrasad)
deleted the
abhi-fix-npm-trusted-publishing-token
branch
Braintrust eval report
|
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
2 participants
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.
Clear NODE_AUTH_TOKEN and NPM_TOKEN on the npm publish steps so npm uses GitHub OIDC trusted publishing instead of an injected token from setup-node.
The failed autoevals@0.3.0 release had a NODE_AUTH_TOKEN present during npm publish, which caused npm to attempt token-based publishing and return a misleading 404 for the package. This mirrors the working publish setup in braintrust-sdk-javascript while preserving provenance publishing for both stable and prerelease releases.