Skip to content

ci(publish): stop gating the crate publish on the shared tag check - #21

Merged
shinaoka merged 1 commit into
mainfrom
ci/publish-tag-validation
Sep 20, 2026
Merged

shinaoka merged 1 commit into
mainfrom
ci/publish-tag-validation

Conversation

@shinaoka

Copy link
Copy Markdown
Member

The v0.10.1 publish run failed every job before reaching crates.io:

Error: Git tag version (0.10.1) does not match Cargo.toml version (t4a-cubecl-zspace@0.10.1).

The shared tracel-ai/github-actions publish-crate workflow runs cargo xtask publish --validate-tag-version, and under the current toolchain the manifest version is reported as <name>@<version>, so a correct tag never matches. The reusable workflow already exposes a tag-validation input, so this turns it off for all 13 published crates; the release commit is what keeps the tag and the workspace version in step.

Needed to publish t4a-cubecl* 0.10.1, which carries the CUDA complex-cast lowering fix (#17) to crates.io consumers of tenferro-rs (tensor4all/tenferro-rs#1833).

🤖 Generated with Claude Code

The shared `publish-crate` workflow validates the release tag by comparing it
against `cargo xtask publish`'s view of the manifest version. The current
toolchain reports that version as `<name>@<version>`, so the comparison
rejects a correct tag:

    Error: Git tag version (0.10.1) does not match Cargo.toml version
    (t4a-cubecl-zspace@0.10.1).

Every job in the v0.10.1 run failed on this before reaching crates.io. Turn
`tag-validation` off so the release can proceed; the release commit is what
keeps the tag and the workspace version in step.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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