ci: two-tier CI + gating Linux dist build + rolling edge prerelease#141
Merged
Conversation
Modernize the GitHub Actions setup to match the current Wack pattern (keystore/aviary/hare/metricstore), adapted for a binary (cargo-dist) release instead of a Helm/Docker release. on-push.yml (fast tier) - Run only `format` + `clippy` instead of the full `cargo make ci-flow`, for fast PR feedback. Inline jobs on wack/gh-actions/setup-rust@trunk, replacing the monolithic validate.yml reusable workflow. - Exclude `gh-readonly-queue/**` from push triggers so on-push's fast "⚡ PR Ready" can't satisfy the merge queue's required check before on-merge's comprehensive one finishes. on-merge.yml (comprehensive tier) - `format` + `build` (`cargo make ci-flow`, which already bundles coverage) gate the merge queue. - Add a gating cross-platform release build: `dist-plan` reads the build matrix from `dist plan` at runtime (so it tracks dist-workspace.toml), filtered to Linux targets; `dist-build` builds all Linux dist targets on every merge candidate. macOS builds stay on tags (release.yml) to keep 10x-billed macOS runner spend off the merge queue. - Add `publish-edge`: runs last in the merge group (after format, build, and dist-build are green), reuses the validated dist-build artifacts, and force-updates a rolling `edge` prerelease pointed at the candidate commit. It gates the merge (in pr-ready's needs) with retry on the release upload. `edge` carries Linux binaries; macOS ships with tags. release.yml / dist - Bump cargo-dist 0.29.0 -> 0.32.0 and regenerate release.yml (checkout@v6, upload-artifact@v7, download-artifact@v8, attest@v4). No CROSS_REPO_PAT is configured: multitool's only git dependency (multitool-rust-sdk) is public. The dev-only Dockerfile is removed; it was never published and nothing referenced it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1dfecc6 to
d862147
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Modernize the GitHub Actions setup to match the current Wack pattern
(keystore/aviary/hare/metricstore), adapted for a binary (cargo-dist)
release instead of a Helm/Docker release.
on-push.yml (fast tier)
format+clippyinstead of the fullcargo make ci-flow,for fast PR feedback. Inline jobs on wack/gh-actions/setup-rust@trunk,
replacing the monolithic validate.yml reusable workflow.
gh-readonly-queue/**from push triggers so on-push's fast"⚡ PR Ready" can't satisfy the merge queue's required check before
on-merge's comprehensive one finishes.
on-merge.yml (comprehensive tier)
format+build(cargo make ci-flow, which already bundlescoverage) gate the merge queue.
dist-planreads the buildmatrix from
dist planat runtime (so it tracks dist-workspace.toml),filtered to Linux targets;
dist-buildbuilds all Linux dist targetson every merge candidate. macOS builds stay on tags (release.yml) to
keep 10x-billed macOS runner spend off the merge queue.
publish-edge: runs last in the merge group (after format, build,and dist-build are green), reuses the validated dist-build artifacts,
and force-updates a rolling
edgeprerelease pointed at the candidatecommit. It gates the merge (in pr-ready's needs) with retry on the
release upload.
edgecarries Linux binaries; macOS ships with tags.release.yml / dist
(checkout@v6, upload-artifact@v7, download-artifact@v8, attest@v4).
No CROSS_REPO_PAT is configured: multitool's only git dependency
(multitool-rust-sdk) is public. The dev-only Dockerfile is removed; it
was never published and nothing referenced it.
🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com