fix(ci): add publishConfig for GitHub Packages#8
Merged
Conversation
release-it's npm auth check runs against the default registry unless publishConfig.registry is set. This tells both the auth check and npm publish to use GitHub Packages. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
publishConfig.registrypointing tohttps://npm.pkg.github.com/so release-it's npm auth check and publish target the correct registryWithout this, release-it runs
npm whoamiagainst the default npm registry, which fails becauseGITHUB_TOKENonly authenticates against GitHub Packages.Test plan
🤖 Generated with Claude Code