Skip to content

chore(ci): remove registry cargo-support watch - #40

Merged
cuihtlauac merged 1 commit into
mainfrom
chore/remove-registry-watch
Sep 7, 2026
Merged

cuihtlauac merged 1 commit into
mainfrom
chore/remove-registry-watch

Conversation

@cuihtlauac

Copy link
Copy Markdown
Member

The MCP Registry added cargo (crates.io) as a package registryType in registry v1.8.0 (2026-07-13, modelcontextprotocol/registry#1207). sudo-proxy 1.0.0 is now published to the official registry as io.github.tarides/sudo-proxy with a cargo package (status: active, isLatest), so the temporary tripwire has done its job.

It also would never have flipped GREEN as written: its check counted pre-existing cargo-type servers in the public ?limit=100 listing, which was the wrong signal — the registry accepts cargo regardless of whether any cargo server is already listed.

Removing the workflow per its own header instructions ("WHEN THIS TURNS GREEN: run publish.yml … then delete this workflow").

🤖 Generated with Claude Code

…r published

The MCP Registry added cargo (crates.io) as a package registryType in
registry v1.8.0 (2026-07-13, PR modelcontextprotocol/registry#1207).
sudo-proxy 1.0.0 is now published to the official registry as
io.github.tarides/sudo-proxy with a cargo package, so the tripwire has
served its purpose.

It was also never going to turn GREEN as written: its signal counted
pre-existing cargo-type servers in the public listing, which was the
wrong heuristic — the registry accepts cargo regardless of whether any
cargo server is already listed.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@cuihtlauac
cuihtlauac merged commit d2537d1 into main Sep 7, 2026
12 of 16 checks passed
@cuihtlauac
cuihtlauac deleted the chore/remove-registry-watch branch September 7, 2026 08:43
cuihtlauac added a commit that referenced this pull request Sep 7, 2026
…triage (#42)

Changelog: add a 2026-09-07 entry (release/hygiene, not a ladder rung)
covering the publication of io.github.tarides/sudo-proxy 1.0.0 to the
official MCP Registry once cargo support shipped upstream, the removal
of the obsolete registry-watch tripwire (PR #40), and the
RUSTSEC-2026-0189 not-applicable triage and suppression (PR #41).

Backlog: capture one contingent follow-up — re-evaluate the
RUSTSEC-2026-0189 ignore if an HTTP transport is ever added. The
current assurance-ladder task is unchanged.

Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
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