Skip to content

Conversation

@joshrotenberg
Copy link
Collaborator

Problem

The crates.io publish workflow didn't trigger for the v0.5.0 release.

Root Cause

When GitHub Actions creates a release using GITHUB_TOKEN (which cargo-dist does), it doesn't trigger other workflows' release:published events to prevent infinite loops. This is documented GitHub behavior.

Solution

Add workflow_dispatch as an additional trigger to allow manual publishing when the automatic trigger doesn't fire.

Changes

  • Added workflow_dispatch trigger to publish-crates.yml
  • This allows manual triggering via GitHub UI or CLI

Testing

After merging, we can manually trigger the workflow to publish v0.5.0 to crates.io.

The release:published event doesn't fire when GitHub releases are created
by other actions (using GITHUB_TOKEN), which prevents automatic crates.io
publishing. Adding workflow_dispatch allows manual triggering as a fallback.
@joshrotenberg joshrotenberg merged commit ccb11b6 into main Sep 15, 2025
15 checks passed
@joshrotenberg joshrotenberg deleted the fix/crates-publish-trigger branch September 15, 2025 19:29
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