The Release workflow's "Publish to crates.io" job fails on every tag push (confirmed on both v0.2.0 and now v0.3.0):
error: a value is required for '--token <TOKEN>' but none was supplied
The CARGO_REGISTRY_TOKEN repo/org secret referenced by the publish step is missing or not configured. The GitHub Release object itself is created fine (via a separate step), but the crate is never actually pushed to crates.io, so cargo add rust-rcp (or equivalent) does not resolve to a published version.
This needs a maintainer to add a valid CARGO_REGISTRY_TOKEN secret in repo settings (Settings -> Secrets and variables -> Actions) — not something fixable via a code change. Filed during the 2026-07-27 backlog-fix pass; pre-existing since at least v0.2.0, not introduced by PR #11 (v0.3.0).
The
Releaseworkflow's "Publish to crates.io" job fails on every tag push (confirmed on both v0.2.0 and now v0.3.0):The
CARGO_REGISTRY_TOKENrepo/org secret referenced by the publish step is missing or not configured. The GitHub Release object itself is created fine (via a separate step), but the crate is never actually pushed to crates.io, socargo add rust-rcp(or equivalent) does not resolve to a published version.This needs a maintainer to add a valid
CARGO_REGISTRY_TOKENsecret in repo settings (Settings -> Secrets and variables -> Actions) — not something fixable via a code change. Filed during the 2026-07-27 backlog-fix pass; pre-existing since at least v0.2.0, not introduced by PR #11 (v0.3.0).