chore(ci): daily watch for MCP Registry cargo support#39
Merged
Conversation
The deployed MCP Registry does not yet accept `registryType: cargo` (support is in upstream main since 2026-06-03 but unreleased), so publish.yml's registry step fails with HTTP 400. This temporary scheduled workflow goes red daily while that holds and turns green once any cargo-type server appears in the registry's public API — no auth required. When it turns green: run publish.yml to register io.github.tarides/sudo-proxy, then delete this workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Why
sudo-proxy 1.0.0is published on crates.io, but the MCP Registry listing is blocked: the deployed registry doesn't yet acceptregistryType: cargo(support merged upstream 2026-06-03 but is unreleased — latest registry release is v1.7.9 from 2026-05-12, prod pinned to image tag1.7.9).publish.yml's final step fails withHTTP 400: unsupported registry type: cargo.What this is
A temporary tripwire: a daily scheduled job that goes red while cargo is unsupported and green once it lands. The check is a public
GETon the registry API (counts cargo-type servers) — no auth, no secrets, no OIDC.When it turns green
gh workflow run publish.yml --ref main— registersio.github.tarides/sudo-proxy(cargo publish is skipped since 1.0.0 exists; OIDC handles registry auth).registry-watch.yml.Caveats
🤖 Generated with Claude Code