🚀 release: v0.3.5 — handle rename → scttbnsn (URLs/badges + MCP namespace migration)#12
Merged
Conversation
The GitHub handle rename s-b-e-n-s-o-n → scttbnsn left the published MCP registry identity on the old namespace, which can no longer be verified (the registry checks namespace ownership against the current account). - 🔧 config(registry): mcpName + server.json name → io.github.scttbnsn/portkey-admin-mcp - 🔧 config: bump 0.3.4 → 0.3.5 (package.json, server.json top + packages[0], lockfile) - 📝 docs(changelog): document the 0.3.5 namespace migration - 🔧 config: refresh cached glama-score owner login/slug to scttbnsn npm package name (portkey-admin-mcp) is unchanged, so installs keep working.
scttbnsn
changed the title
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.
GitHub account renamed
s-b-e-n-s-o-n→scttbnsn.URL/badge updates: README badges + clone URL, package.json repository/homepage/bugs, server.json url, glama maintainers, SECURITY/CHANGELOG links, CODEOWNERS, docs.
MCP-registry namespace migration (now included as v0.3.5):
package.json:mcpNameandserver.json:namemovedio.github.s-b-e-n-s-o-n/...→io.github.scttbnsn/portkey-admin-mcp; version bumped 0.3.4 → 0.3.5 (package.json, server.json top + packages[0], lockfile); CHANGELOG entry added; cacheddocs/glama-score/scores.jsonowner login/slug refreshed. The npm package name (portkey-admin-mcp) is unchanged, sonpx portkey-admin-mcpinstalls keep working. Build + 114 tests green locally.Post-merge release steps (require npm auth; registry publish is automatic via OIDC)
The
publish-registryjob authenticates via GitHub OIDC for this repo, which proves ownership of theio.github.scttbnsnnamespace — no secrets needed. It waits for npm 0.3.5 before publishing, and the registry validates the npm package'smcpNamematchesserver.jsonname.