Skip to content

ci(release): bump mcp-publisher to 1.7.6#37

Merged
mathieumaf merged 1 commit into
mainfrom
ci/bump-mcp-publisher-1.7.6
Apr 30, 2026
Merged

ci(release): bump mcp-publisher to 1.7.6#37
mathieumaf merged 1 commit into
mainfrom
ci/bump-mcp-publisher-1.7.6

Conversation

@mathieumaf
Copy link
Copy Markdown
Contributor

@mathieumaf mathieumaf commented Apr 30, 2026

Summary

  • Bump MCP_PUBLISHER_VERSION in .github/workflows/release.yml from 1.6.0 to 1.7.6 (latest, published 2026-04-30).
  • Required by registry#1229, a documented breaking change: the registry now validates the OIDC aud claim against MCP_REGISTRY_GITHUB_OIDC_AUDIENCE, and the publisher CLI must derive the audience from --registry. Old binaries fail with invalid audience: expected …, got […] once the prod registry rolls the matching validation.
  • Asset name (mcp-publisher_linux_amd64.tar.gz) and checksums file (registry_1.7.6_checksums.txt) layout are unchanged, so the existing download / verification logic continues to work.
  • No changes to the publisher CLI commands we use (login github-oidc, publish).

Test plan

  • CI on this PR passes (lint / typecheck / format / build / test).
  • On the next release (merge of a Version Packages PR), confirm the workflow:
    • downloads mcp-publisher_linux_amd64.tar.gz from the v1.7.6 release,
    • verifies its sha256 against registry_1.7.6_checksums.txt,
    • completes mcp-publisher login github-oidc and mcp-publisher publish against the production registry without an invalid audience error.

Required for the new GitHub OIDC audience binding (registry PR
modelcontextprotocol/registry#1229) — older binaries get rejected
with `invalid audience` once the production registry rolls the
matching server-side validation.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 30, 2026

Warning

Rate limit exceeded

@mathieumaf has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 34 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6deae4b1-3c8a-4c73-972f-139e2842bbb0

📥 Commits

Reviewing files that changed from the base of the PR and between 2b6fce2 and 4d82877.

📒 Files selected for processing (1)
  • .github/workflows/release.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/bump-mcp-publisher-1.7.6

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 49 minutes and 34 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 30, 2026

⚠️ No Changeset found

Latest commit: 4d82877

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@mathieumaf mathieumaf merged commit b5a523c into main Apr 30, 2026
7 checks passed
@mathieumaf mathieumaf deleted the ci/bump-mcp-publisher-1.7.6 branch April 30, 2026 08:26
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