fix(ci): bump mcp-publisher to v1.7.9 — fixes recurring MCP Registry OIDC audience failure#299
Open
guyernest wants to merge 1 commit into
Open
fix(ci): bump mcp-publisher to v1.7.9 — fixes recurring MCP Registry OIDC audience failure#299guyernest wants to merge 1 commit into
guyernest wants to merge 1 commit into
Conversation
… audience The "Publish to MCP Registry" job has failed on every release since v2.10.0 with: invalid audience: expected https://registry.modelcontextprotocol.io, got [mcp-registry] mcp-publisher v1.5.0 mints its github-oidc token with the legacy "mcp-registry" audience; the registry now requires the URL audience, which newer publisher releases send. Non-blocking historically (crates.io publish is a separate job), but the registry listing has been stuck since 2.9.x. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
The Publish to MCP Registry job in
release.ymlhas failed on every tagged release since v2.10.0 (v2.10.0, v2.12.0, v2.14.0, and today's v2.15.0 — run 29118681797) with:Root cause: the workflow downloads
mcp-publisherv1.5.0, which mints itsgithub-oidctoken with the legacymcp-registryaudience. The registry now requires the URL audience, which current publisher releases send. This PR bumps the pin to v1.7.9 (latest, stable since 2026-05-12).One line, workflow-only — no crate changes. Historically non-blocking (crates.io publish is a separate job and has succeeded every time), but the MCP Registry listing has been stuck on a pre-2.10 version as a result.
Verification
mcp-publisher login github-oidcstep.mcp-publisher login github+publishfrom a checkout of the tag.🤖 Generated with Claude Code