feat(publish): support registry priority configuration#132
Merged
Conversation
- Remove hardcoded DEFAULT_NPM_REGISTRY constant - Add resolveRegistry utility to handle registry resolution with priority: CLI parameter > package.json publishConfig.registry > npm config - Update GitHub Actions workflows to configure npm auth tokens - Add comprehensive unit tests for registry resolution - Update related type definitions to make registry optional - Fix eslint errors: extract magic number constant and fix type assertion 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Tecvan-fe
enabled auto-merge
January 7, 2026 13:00
dragooncjw
approved these changes
Jan 7, 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
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.
🤖 Generated with Claude Code