Commit graph

5 commits

Author SHA1 Message Date
Austin Schaefer
ff91960b7b Force musl targets for cargo-binstall to avoid GLIBC mismatch
All checks were successful
CI / ci (pull_request) Successful in 1m47s
The glibc-linked prebuilt cargo-make binary requires GLIBC 2.39,
newer than what's on the node:20-bookworm image. Musl binaries
are statically linked and avoid the mismatch.
2026-07-29 16:24:50 +02:00
Austin Schaefer
3788eafa88 Speed up CI by caching rustup toolchain and using cargo-binstall
Some checks failed
CI / ci (pull_request) Failing after 26s
Cache ~/.rustup so the toolchain isn't reinstalled every run, and
install cargo-make/cargo-audit via cargo-binstall instead of
compiling them from source each time.
2026-07-29 16:12:18 +02:00
Austin Schaefer
1cda8b6f50 Only trigger CI push runs on master to avoid duplicate builds
All checks were successful
CI / ci (pull_request) Successful in 10m41s
Pushing to a branch with an open PR fired both the push and
pull_request triggers for the same commit. pull_request already
covers feature-branch commits, so push only needs to cover master.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-29 12:29:11 +02:00
Austin Schaefer
4e65ef3843 Fix CI job: run on default node image instead of rust:latest
Some checks failed
CI / ci (push) Failing after 20m50s
CI / ci (pull_request) Failing after 1h20m38s
The rust:latest container has no Node.js, but actions/checkout@v4 and
actions/cache@v4 are JS actions that require it to execute at all,
so the job failed before any cargo/fmt steps ran. Use the default
docker runner image and install the Rust toolchain via rustup instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-29 12:25:09 +02:00
Austin Schaefer
4b751dc246 Add Forgejo Actions CI workflow
Runs cargo fmt/clippy/test/audit via the existing cargo-make ci task on every push and pull request.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-29 12:03:01 +02:00