release: v1.15.1 - #369
Merged
Merged
Conversation
main carries rebased TWINS of develop's commits (its v1.15.0 release commit is 483a99c, develop's is ab69af7), so the branches share no recent ancestry and a rebase promotion comes back CONFLICTING. Same divergence cfd92fa reconciled at v1.15.0; this commit does the same for v1.15.1 rather than restructuring the release topology mid-cut. This commit pins main's tree byte-identical to develop's release commit fc2bb36 (tree fdf6d1b), preserving the verify-trees-then-tag invariant. Content differences: none. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Promote to main for the v1.15.1 release.
Patch release: #364 — an unreachable worker API no longer aborts the run (
tune/autotunesampling died with exit 7 on any bash), nor prints spurious[ERROR] rigforge abortedon bash 3.2 while succeeding. Landed as #366.Why this is a reconcile branch, not
developdirectlymaincarries rebased twins of develop's commits — its v1.15.0 release commit is483a99c, develop's isab69af7— so the two share no recent ancestry andgh pr merge --rebaseon a develop→main PR comes back CONFLICTING (that was #368, now closed). Same divergencecfd92fareconciled at v1.15.0.This branch's tree is pinned byte-identical to develop's release commit
fc2bb36:Content differences from develop: none. That preserves RELEASING.md's verify-trees-then-tag invariant. I did not restructure the release topology mid-cut — worth doing deliberately later, since this recurs every release.
Release gate
e2e-real on miner-3 (EPYC 7642): provision 7 / verify 38 / control 8 / upgrade 15 / perf 2 / teardown 13 — all PASS.
Gated on miner-3 rather than miner-0 because miner-0 has Secure Boot enabled, so kernel lockdown denies MSR writes and doctor cannot pass — pre-existing and environmental, reproduces identically on the v1.15.0 tag. (v1.15.0 was itself gated on miner-2, so RELEASING.md's "miner-0 every time" is already stale.)
One transient verify failure on the first attempt, filed as #367 rather than silently re-run to green.
CI was green on
44ca68dincluding the macOS bash 3.2 job.