build(ci): explicitly set GitHub Packages registry in publish step #3
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
lxcid
force-pushed
the
lxcid/fix-github-publish
branch
from
8c4d3d5 to
abfc5e5
Compare
🦋 Changeset detectedLatest commit: 44df9ff The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
The GitHub Packages publish step was incorrectly attempting to publish to npm registry instead of GitHub Packages. This adds the explicit --registry flag to ensure it publishes to the correct registry. Without this flag, the setup-node registry configuration was being overridden by the prepublishOnly script, causing the publish to target npm instead of GitHub Packages.
lxcid
force-pushed
the
lxcid/fix-github-publish
branch
from
abfc5e5 to
cffcdae
Compare
lxcid
force-pushed
the
lxcid/fix-github-publish
branch
2 times, most recently
from
0376208 to
ce42540
Compare
lxcid
force-pushed
the
lxcid/fix-github-publish
branch
from
ce42540 to
44df9ff
Compare
lxcid
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 GitHub Packages publish step was incorrectly attempting to publish to npm registry instead of GitHub Packages. This adds the explicit --registry flag to ensure it publishes to the correct registry.
Without this flag, the setup-node registry configuration was being overridden by the prepublishOnly script, causing the publish to target npm instead of GitHub Packages.