[codex] Fix trusted publishing runtime#41
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.
Summary
Fixes the trusted-publishing runtime used by the Release workflow after #40.
The failed Release run showed
changesets/actiondetected OIDC, butpnpm publish --filter @godaddy/clistill failed withENEEDAUTHbecause the runner was on Node 22/npm 10. npm trusted publishing requires npm 11.5.1+, andgodaddy/javascriptsucceeds with Node 24/npm 11.Changes:
repositorymetadata matchinggodaddy/cli, which npm trusted publishing docs call out for GitHub matchingValidation
pnpm publish --filter @godaddy/cli --dry-run --no-git-checks