Add registry-url to release workflow#1146
Merged
graygilmore merged 2 commits intomainfrom Mar 13, 2026
Merged
Conversation
Our release isn't currently working and this is one of the pieces that's missing from the documentation that we haven't added.
graygilmore
force-pushed
the
gg-fix-release
branch
from
a44769e to
363e5ae
Compare
kdaviduik
approved these changes
Mar 13, 2026
Contributor
kdaviduik
left a comment
kdaviduik
left a comment
There was a problem hiding this comment.
LGTM, i remember having to do the same thing in Hydrogen
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.
Our release workflow is currently failing and documentation seems to suggest that we should be using the
registry-urlattribute when setting up Node.Additionally I ran
npm pkg fixagainst all of thepackage.jsonfiles in the repo after seeing warnings in the action logs.