From cf5dacb4e9de29d16a897cfe3cfbabd02c86bc36 Mon Sep 17 00:00:00 2001 From: Yasunobu <42543015+P4suta@users.noreply.github.com> Date: Sun, 31 May 2026 11:08:18 +0900 Subject: [PATCH] build(afm): install bacon explicitly from source MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit bacon ships no prebuilt binaries (crates.io-source-only), so it previously resolved only via cargo-binstall's implicit `compile` fallback — the last link in binstall 1.19.x's default strategy chain (`crate-meta-data,quick-install,compile`). Make the source install explicit with `cargo install --locked bacon` so the bacon layer no longer depends on binstall's default strategies: a future default change, or adopting aozora's fail-fast `--strategies` policy on the batch, would otherwise silently break it. No behaviour change today — binstall already compiled it. Mirrors aozora #55. Co-Authored-By: Claude Opus 4.8 (1M context) --- Dockerfile | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/Dockerfile b/Dockerfile index 54a18d1..1253b09 100644 --- a/Dockerfile +++ b/Dockerfile @@ -89,8 +89,17 @@ RUN cargo binstall --no-confirm --locked --root /usr/local \ cargo-edit \ cargo-release -# bacon — kept in its own layer (separate churn axis from the test/lint tiers). -RUN cargo binstall --no-confirm --locked --root /usr/local bacon +# bacon (the background compiler behind `just watch`) ships NO prebuilt +# binaries on its GitHub releases — it is crates.io-source-only. Every +# binstall line above resolves a tool that *does* publish prebuilts; bacon +# would only ever land via binstall's implicit `compile` fallback (the last +# link in its default strategy chain). Install it explicitly from source +# instead, so the source build is a deliberate, visible choice rather than a +# silent fallback a future binstall default-strategy change could drop. Kept +# in its own layer (separate churn axis from the test/lint tiers). Mirrors +# aozora #55, which made the same crate explicit after its binstall batch +# dropped `compile` from `--strategies`. +RUN cargo install --locked bacon # git-cliff for CHANGELOG generation — kept separate for the same reason. RUN cargo binstall --no-confirm --locked --root /usr/local git-cliff