Skip to content

fix: make GitHub release depend on successful crate publish#43

Merged
mickvandijke merged 1 commit intomainfrom
fix/release-workflow-dependencies
Mar 25, 2026
Merged

fix: make GitHub release depend on successful crate publish#43
mickvandijke merged 1 commit intomainfrom
fix/release-workflow-dependencies

Conversation

@jacderida
Copy link
Collaborator

Summary

  • Adds publish-crate to the release job's needs list so a GitHub release is only created if crate publishing succeeds

Test plan

  • Verify release workflow graph shows the correct dependency chain

🤖 Generated with Claude Code

The release job previously only depended on validate and sign, meaning a
GitHub release could be created even if crate publishing failed.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings March 24, 2026 23:23
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the release workflow so creating the GitHub Release is gated on a successful crates.io publish, preventing “release artifacts published on GitHub but crate publish failed” situations.

Changes:

  • Add publish-crate to the release job’s needs so release only runs if crate publishing succeeds.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mickvandijke mickvandijke merged commit bee8089 into main Mar 25, 2026
15 checks passed
@mickvandijke mickvandijke deleted the fix/release-workflow-dependencies branch March 25, 2026 08:32
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.

3 participants