Skip to content

ci(release): tag after build + fix rustup toolchain setup#85

Merged
Mikola Lysenko (mikolalysenko) merged 1 commit into
mainfrom
fix-release-workflow
May 27, 2026
Merged

ci(release): tag after build + fix rustup toolchain setup#85
Mikola Lysenko (mikolalysenko) merged 1 commit into
mainfrom
fix-release-workflow

Conversation

@mikolalysenko
Copy link
Copy Markdown
Collaborator

Summary

  • Move the tag job to run after build succeeds, so a failed build no longer leaves a dangling tag behind. All publish jobs (github-release, cargo-publish, npm-publish, pypi-publish) now depend on tag, so we never half-publish without one.
  • Replace dtolnay/rust-toolchain with direct rustup show + rustup target add. The dtolnay action can't auto-detect the channel when pinned by SHA (it normally parses it from the ref name like @stable), which caused the release run to fail with 'toolchain' is a required input. This matches the pattern already used in ci.yml.

Test plan

  • Trigger the Release workflow with dry-run: true and confirm all matrix targets build successfully
  • Confirm no v* tag is created on a dry-run
  • On a real release, confirm the tag is created only after all builds pass, and publish jobs run after the tag

🤖 Generated with Claude Code

Tag now runs after build succeeds so a failed build no longer leaves
behind a dangling tag. All publish jobs depend on tag, so we never
half-publish without one.

Replaces dtolnay/rust-toolchain (which can't auto-detect the channel
when pinned by SHA) with direct rustup invocation, matching the pattern
already used in ci.yml.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mikolalysenko Mikola Lysenko (mikolalysenko) merged commit dde67db into main May 27, 2026
32 checks passed
@mikolalysenko Mikola Lysenko (mikolalysenko) deleted the fix-release-workflow branch May 27, 2026 14:23
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.

2 participants