Fix v6 npm publishing registry and release retry - #47
Merged
Merged
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
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.
The v6 GitHub release built successfully, but neither package appeared on npm. The first publish run stopped here:
bin/publish-npmruns under Yarn throughscripts/publish-packages.ts:96, so npm inherited Yarn's registry instead of targeting npmjs. I set the npmjs registry explicitly for the version lookup and publish atbin/publish-npm:22,59. I also made.github/workflows/publish-npm.ymlable to retry both packages and attach the MCP bundle to an existing release. That targets the registry mismatch shown in the log, without changing package contents or asking for an npm token.The retry published both packages at 6.0.0. I corrected the changelog at the same time: the old app and bridge namespace names were on unreleased
next, not in published v5.Tag
@indentto continue the conversation here.