Repository navigation
Delete orphaned namespace after GitHub org rename #1191
Description
I renamed my GitHub org from Utilify-io to utilify-io right after publishing. The old entry io.github.Utilify-io/utilify-mcp is now orphaned — I cannot authenticate against the old capitalized namespace (my current token only sees the renamed lowercase org), but the old entry is still holding the remote URL https://utilify.io/mcp, which prevents me from publishing the lowercase canonical version io.github.utilify-io/utilify-mcp. Could an admin delete the capital-U entry so I can republish under the correct namespace? Thanks.
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-]Delete orphaned namespace after GitHub org rename[/-][+]Delete orphaned namespace after GitHub org rename[/+]rdimitrov commentedon Apr 24, 2026
Hey, this is a manifestation of the case-sensitivity issue tracked in #689, since
io.github.Utilify-io/*permissions were created case-sensitively, renaming your org to lowercase on GitHub leaves the old entry unreachable. The proper fix is normalizing theio.github.*namespace to lowercase in both permission checks and storage (being worked on in #689), which would structurally resolve this. Also touches #1193 for the remote-URL-collision side.Keeping this open as a concrete symptom of #689. Will circle back once those land.
rdimitrov commentedon Oct 23, 2026
Soft-deleted
io.github.Utilify-io/utilify-mcp@0.1.0with a migration message pointing toio.github.utilify-io/utilify-mcp. Verified the historical payload is unchanged and the old entry is absent from default discovery; the lowercase replacement remains unpublished. The public integration repository's history maps to this issue author's numeric GitHub account and documents the same service. Please retry publishing the lowercase name. Closing this concrete cleanup; the general case-sensitivity and URL-collision work remains tracked in #689 and #1193.