Skip to content

chore(release): regenerate release.yml for cargo-dist v0.26.0 prebuilt binary#119

Merged
ferhimedamine merged 1 commit into
mainfrom
fix/regenerate-cargo-dist-workflows
Jul 16, 2026
Merged

chore(release): regenerate release.yml for cargo-dist v0.26.0 prebuilt binary#119
ferhimedamine merged 1 commit into
mainfrom
fix/regenerate-cargo-dist-workflows

Conversation

@ferhimedamine

Copy link
Copy Markdown
Contributor

Problem

After merging PR#117 (dist-workspace.toml fix), the Release workflow still fails:

× release.yml has out of date contents and needs to be regenerated

The locally-compiled cargo-dist v0.26.0 (via cargo install) generates old-format workflow files, while the GitHub prebuilt binary (downloaded via installer in CI) generates a newer format. The dist plan command in CI detects this mismatch and aborts.

Fix

Regenerate .github/workflows/release.yml to match what the prebuilt dist binary v0.26.0 expects. Key changes:

  • New header with copyright/license comments
  • pull_request trigger added (for plan-only runs on PRs)
  • Tag pattern updated: **[0-9]+.[0-9]+.[0-9]+*
  • Dynamic matrix from plan output (removes hardcoded target list)
  • Uses cached dist binary across jobs (upload-artifact instead of actions/cache)
  • Host job now creates GitHub Release directly via gh release create
  • Homebrew formula publishing extracted to dedicated job
  • New announce job
  • Removed publish-crate job (crates.io publish was not working anyway)

After merge

Delete the current v0.7.0 tag and retag on the new HEAD → Release workflow should pass.

Closes DAK-7451 (second root cause — workflow regeneration needed after dist-workspace.toml fix).

…t binary compatibility

The locally-compiled cargo-dist v0.26.0 and the GitHub prebuilt binary
generate different workflow formats. The plan step was detecting the old
format and failing with 'out of date contents'. Regenerated from the diff
shown in CI logs to match what the prebuilt dist binary expects.

Closes DAK-7451 (second root cause).
@ferhimedamine ferhimedamine added the auto-merge Auto-merge when CI passes label Jul 16, 2026
@ferhimedamine
ferhimedamine merged commit b0618c3 into main Jul 16, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge Auto-merge when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant