ci: bump mcp-publisher to v1.7.6#495
Conversation
The MCP Registry shipped a breaking OIDC-audience change in v1.7.6 (modelcontextprotocol/registry#1229), causing Login to MCP Registry to fail with "invalid audience: expected https://registry.modelcontextprotocol.io, got [mcp-registry]" on v2.11.0 and v2.12.0 publish runs. v1.7.6 of the publisher CLI sends the new audience. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe MCP Publisher binary version used in the publish workflow is upgraded from v1.4.0 to v1.7.6, allowing the workflow to use the latest publisher release during registry publishing. ChangesPublish Workflow Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 9/10 reviews remaining, refill in 6 minutes. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #495 +/- ##
=======================================
Coverage 86.64% 86.64%
=======================================
Files 49 49
Lines 7071 7071
Branches 2123 2123
=======================================
Hits 6127 6127
Misses 284 284
Partials 660 660
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Bundle ReportBundle size has no change ✅ |
Summary
mcp-publisherCLI from v1.4.0 to v1.7.6 in .github/workflows/publish.ymlWhy
The MCP Registry shipped a breaking OIDC-audience change in v1.7.6 (registry#1229) on 2026-04-30. The registry now rejects the audience that the v1.4.0 publisher sends:
This caused the
Login to MCP Registrystep to fail on the v2.11.0 and v2.12.0 release publishes. The npm publish itself succeeded both times (both versions are live on npm), so user-facing impact is limited to the MCP Registry being out of date.Test plan
workflow_dispatchwithpublish_to_registry: trueto backfill v2.12.0 (and v2.11.0) on the MCP Registry🤖 Generated with Claude Code
Summary by CodeRabbit