Skip to content

fix(ci): align MCP registry namespace with GitHub OIDC - #453

Merged
PascaleBeier merged 2 commits into
mainfrom
fix/mcp-registry-oidc-namespace-20261103
Nov 3, 2026
Merged

PascaleBeier merged 2 commits into
mainfrom
fix/mcp-registry-oidc-namespace-20261103

Conversation

@PascaleBeier

Copy link
Copy Markdown
Collaborator

Registry publication for 2.16.0 and 2.16.1 authenticates successfully but returns 403: GitHub OIDC grants io.github.HitKeep/*, while server.json requests the legacy personal namespace. Use io.github.HitKeep/hitkeep and validate the selected release tag's namespace before schema validation and the existing authenticated publication.

This proposes a new public registry identity for maintainer approval before merge/publication. The legacy registry listing, runtime implementation name, connection URLs and authorization remain unchanged. Release notes explain compatibility, the new-release requirement, and exact-version registry readback; old tags retain their original metadata. No publication was performed. Website registry wording should be updated after the organization entry is verified.

Validation: 53 release-script tests passed, including execution of the actual namespace preflight with valid and invalid fixtures. Canonical complete plan 4e6cecd057872432a7439a11, run 20261103T075532-860cb77a, finished passed / exit 0: go-format, go-fix, go-lint, go-vet, go-staticcheck, go-race-server, goreleaser-check, mcp-audit, mcp-schema, developer-docs, govulncheck, zizmor, actionlint, helm-lint (actionlint reused passing evidence from the unchanged-source preflight).

Official namespace authentication and GitHub Actions publishing define the OIDC ownership rule.

@PascaleBeier
PascaleBeier merged commit edd00e2 into main Nov 3, 2026
19 checks passed
@PascaleBeier
PascaleBeier deleted the fix/mcp-registry-oidc-namespace-20261103 branch November 3, 2026 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant