ci(release): apply #700 boost torn-cache pattern to release.yml (before v0.2.1 re-tag) - #702
Merged
Merged
Conversation
…st sentinel on release.yml Extends the #700 boost torn-cache fix from build.yml to release.yml so the v0.2.1 all-coin re-tag does not re-hit the 1.90.0 torn-header flake. Linux and Windows package lanes (the two Conan-using lanes): - per-job CONAN_HOME=${{ runner.temp }}/conan2 so concurrent coin cells on the shared c2pool-build host build Boost into isolated caches (root-cause fix). - replace `conan profile detect --force`+cppstd sed with committed profiles via -pr:a=ci/conan/{linux-gcc13,windows-msvc}.profile (stable package_id). - commit conan.lock and pass --lockfile=conan.lock on every install (boost 1.90.0 pinned); cache keys now hash profile + lockfile. - add the Boost header-integrity sentinel gate before the coin build. macOS lanes build against Homebrew deps (no Conan), so they cannot hit the torn-cache flake and are left unchanged; macos-clang.profile is committed for provenance / a future macOS->Conan migration only. checksums job does no build. VM217 Windows shell port (07-14) preserved.
This was referenced Jul 14, 2026
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
1 participant
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.
Follow-up to #700 (which landed build.yml-only). master release.yml still had the flaky pattern (
conan profile detect --forceat Linux ~L120 / Windows ~L490, shared ~/.conan2, no lockfile), so the v0.2.1 all-coin re-tag would re-hit the boost 1.90.0 torn-header flake. This extends the #700 pattern to release.yml.Linux + Windows package lanes (the two Conan-using lanes)
CONAN_HOME=${{ runner.temp }}/conan2— each concurrent coin cell on the shared c2pool-build host builds Boost into an isolated cache; this is the root-cause fix for the torn ~/.conan2.conan profile detect --force+ cppstd sed with-pr:a=ci/conan/linux-gcc13.profile(already committed) and newci/conan/windows-msvc.profile(msvc 194, cppstd=20). Stable package_id, no wrong-config prebuilt fallback.--lockfile=conan.lockon every install; cache keys now also hash the profile + lockfile.Not changed (by design)
ci/conan/macos-clang.profileis committed for provenance / a future macOS→Conan migration only; the macOS lane is untouched.Scope note
build.yml is already green with the #700 pattern; I deliberately did not re-touch it here to keep this PR release-scoped. Wiring build.yml to also consume conan.lock is a clean follow-up if you want lockfile enforcement fleet-wide.
Workflow-scope → your review + operator tap before merge. No self-merge.