[adriencaccia]

memtrack and exec-harness now ship inside the runner, so dist only releases codspeed-runner and no longer needs a custom draft job and hand edits to keep subtool releases from becoming "latest". dist creates the release itself, cache-builds = false replaces the hand-removed rust-cache step, and without allow-dirty a PR whose release.yml differs from what dist generate produces fails dist's plan (checked locally: a bumped pin makes dist plan exit with "run 'dist init' to update the file").

Case	Before	Now
Stable release vX.Y.Z	A custom job drafts it, a hand edit undrafts it, post-announce marks it latest	dist creates it as latest
Alpha vX.Y.Z-alpha.N	Published as a regular release, not latest	Published as a pre-release
PR release build	Installer and checksums skipped	Built
release.yml differs from the config	Accepted	dist plan fails the PR
Action pin bump in release.yml	Dependabot PR	Bump [dist.github-action-commits], then dist generate
Regenerating release.yml	dist generate, then redo 2 hand edits	dist generate

Closes COD-4268

[codspeed]

Merging this PR will not alter performance

2 warnings

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ 8 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 53 untouched benchmarks
⏩ 6 skipped benchmarks¹

---

_{Comparing cod-4268-release-the-runner-with-dists-defaults-now-that-it (eb9d9f9) with main (25c26e7)}

Footnotes

1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Lets cargo-dist create runner releases without a custom draft job or hand-edited workflow steps.

• Runner tags now create releases directly from the built artifacts.
• The generated release workflow now follows the dist config.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[PR or version tag] --> B[Plan]
  B --> C[Build platform artifacts]
  C --> D[Build installers and checksums]
  D --> E{Version tag?}
  E -->|No| F[Keep workflow artifacts]
  E -->|Yes| G[Create GitHub release]
  G --> H[Publish executable hashes and refresh allowlist]
  H --> I{Stable release?}
  I -->|Yes| J[Trigger action version bump]

Loading

_{Reviews (1) · Last reviewed commit: "ci: fail PRs whose release.yml differs f..." · Reviewed by Greptile}