ci(publish): use tool versions for Node release runtime#199
Merged
Abhijeet Prasad (AbhiPrasad) merged 1 commit intoJun 9, 2026
Merged
Conversation
Configure the JavaScript publish workflow to read Node from .tool-versions and add the same Node, npm, and pnpm tool versions used by the working braintrust-sdk-javascript publish flow. The previous rerun cleared npm token environment variables correctly, but the GitHub runner's Node 22 image used npm 10.9.8 and failed trusted publishing with ENEEDAUTH. Moving the publish workflow to Node 24 gives it npm 11 support for GitHub OIDC trusted publishing without a one-off npm install step.
Braintrust eval report
|
Caitlin Pinn (cpinn)
approved these changes
Jun 9, 2026
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.
Configure the JavaScript publish workflow to read Node from .tool-versions and add the same Node, npm, and pnpm tool versions used by the working braintrust-sdk-javascript publish flow.
The previous rerun cleared npm token environment variables correctly, but the GitHub runner's Node 22 image used npm 10.9.8 and failed trusted publishing with ENEEDAUTH. Moving the publish workflow to Node 24 gives it npm 11 support for GitHub OIDC trusted publishing without a one-off npm install step.