Publish under io.github.CDVolvik, not the old account - #56
Merged
Merged
Conversation
Same fix as the badge commit on this branch: the repo moved to CDVolvik but server.json still declared io.github.kushaim/practice-fusion-mcp and a kushaim repository URL. CI publishes over OIDC and derives the namespace from the repo owner, so the declared name has to match the actual owner. End users are unaffected -- the registry name is not what their client resolves.
4 tasks
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 repo moved from kushaim to CDVolvik (2026-08-05); PR #55 fixed the README badges. This finishes the move: every remaining live identity reference now points at CDVolvik.
Note for the next release: npm 0.4.0 was published with the old mcpName, so the next npm + registry publish should bump to >= 0.4.1 for the new identity to take effect there. npx users are unaffected either way.
Second-model review ran (codex): flagged the version-match issue above and the stale PHASE-0 link; both addressed.