fix: Authenticate setup-node against npm.pkg.github.com#780
Merged
Conversation
🦋 Changeset detectedLatest commit: 314b171 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
codingshinoby
approved these changes
Jun 5, 2026
colinbird
approved these changes
Jun 5, 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
3 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.
The 'Generate SDK and diff vs main' workflow has been failing on every release PR because
actions/setup-nodedoesn't write authentication config for npm.pkg.github.com when there's no registry-url/scope set. The subsequentnpm cithen gets a 401 trying to download@rebilly/regenerator.This PR adds the same registry-url and scope config that update.yaml already uses so
npm cican pull@rebilly/regeneratorfrom GitHub Packages.