feat: display registry URL when publishing packages #7020
+28
−2
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
Display the target registry URL at the start of yarn npm publish to help users verify their configuration and debug authentication errors Closes yarnpkg#6191
clemyan
reviewed
Dec 17, 2025
- Include tag in initial publish message - Remove redundant registry/tag info from dry-run message
clemyan
approved these changes
Dec 18, 2025
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.
What's the problem this PR addresses?
When using
yarn npm publishwith private registries, users have no way to verify which registry URL Yarn is targeting. When authentication fails with errorYN0033: No authentication configured for request, it's impossible to determine whether the issue is with the token configuration or an incorrect registry URL.This is especially problematic when migrating from npm to Yarn, as the configuration methods differ significantly.
Closes #6191
How did you fix it?
Added a log message at the beginning of the publish process that displays the target registry URL.
Implementation:
report.reportInfo(MessageName.UNNAMED,Publishing to ${registry})inpublish.tsright after the report startsExample output:
Checklist