fix(ci): send User-Agent in crates.io poll; make publish re-runnable#38
Merged
Conversation
The crates.io API returns HTTP 403 without a User-Agent, so the "wait for crate to be live" poll in publish.yml failed every attempt and aborted the job before the MCP Registry steps ran (the v1.0.0 crate published fine; only the registry listing was skipped). - Send a User-Agent on all crates.io API requests. - Add a workflow_dispatch trigger and derive the version from Cargo.toml so the workflow can be run manually (e.g. to register the server when the crate is already published). - Skip `cargo publish` when the version is already on crates.io, so dispatch re-runs don't fail on an existing version. 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.
Problem
The
v1.0.0Publish run published the crate to crates.io successfully (Trusted Publishing works), but the "Wait for crate to be live" poll failed every attempt, aborting the job before the MCP Registry steps ran. Root cause: the crates.io API returns HTTP 403 without aUser-Agentheader, and the poll usedcurl -fsSwith none.Net result:
sudo-proxy 1.0.0is live on crates.io, but the server is not yet registered in the MCP Registry.Fix
User-Agenton all crates.io API requests.workflow_dispatchtrigger and derive the version fromCargo.toml, so the workflow can be run manually to (re)register the server when the crate is already published.cargo publishwhen the version is already on crates.io, so dispatch re-runs don't fail on an existing version.After merge
Run this workflow via
workflow_dispatchonmainto registerio.github.tarides/sudo-proxy1.0.0 (cargo publish is skipped; OIDC handles the registry auth).🤖 Generated with Claude Code