ci: add tag-triggered release workflow#37
Merged
Merged
Conversation
Adds a release workflow conforming to the umbrella SDK release pipeline contract (u5c-factory reference/sdk-pipeline-requirements.md): a v* version tag triggers build -> test -> publish, the crate version is derived from the tag, and the crate is published to crates.io. Verification: workflow YAML syntactically validated only; not executed and the crate not built this session. Requires the CARGO_REGISTRY_TOKEN repository secret before the first release.
scarmuega
added a commit
that referenced
this pull request
May 21, 2026
rust-sdk release.yml merged (#37) before the umbrella contract settled on manifest-as-source-of-truth versioning. Bring it in line with the other SDKs: - Add a verify job that checks the pushed tag equals the Cargo.toml version and fails fast on mismatch, before build/test/publish. - Drop the step that rewrote Cargo.toml from the tag; cargo publish no longer needs --allow-dirty. - Point the umbrella contract comment at the renamed reference/sdk-pipeline.md. Verification: workflow YAML syntactically validated only; not executed.
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
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.
What
Adds a
release.ymlworkflow conforming to the umbrella SDK release pipeline contract (u5c-factory→reference/sdk-pipeline-requirements.md).v*version tagverify→build→test→publish, each gating the nextverifyjob checks the pushed tag against theCargo.tomlcrate version and fails the release on mismatch — the manifest is the source of truth; the workflow never edits itVerification
Workflow YAML syntactically validated only. Not executed and the crate not built this session — the pipeline can only be exercised by a real tag push.
Operational prerequisite
The
CARGO_REGISTRY_TOKENrepository/org secret (a crates.io API token) must exist before the first release.