Repository navigation
Release pending: rigforge: 1.18.0 (after the pithead 2.0.0 soak) #564
Description
Owner ruling on pithead#2602 (2026-10-02): RigForge's next release is 1.18.0, cut after the pithead 2.0.0 soak, from the develop code the 2.0.0 image bakes (pinned by pithead#3029). Nothing else goes into it.
At release time (the owner's action, per RELEASING.md):
CHANGELOG.md: remove the unreleased## [1.17.4] - 2026-09-08section. Fold its Fail closed across the combined appliance release gates #491 entry and every change since v1.17.3 into a new## [1.18.0] - <date>. Among them: Deprecate macOS as a supported platform #504 macOS deprecation, tier4 contract: configured worker never exposes enriched feed #507/fix(control): control implies the sister enriched feed (#507) #517, fix(control): always record a terminal outcome for a claimed apply #511, One access token per consuming stack, so a bench borrow never needs prod's token #516/One access token per consuming stack (ACCESS_TOKENS) (#516) #521ACCESS_TOKENS, control-upgrade oneshot has no TimeoutStartSec, but a rebuild can take ~10 minutes #510/fix(control): the upgrade oneshot opts out of the 90s start timeout #524, fix(api): serve the control changes/ ring on the unauthenticated read feed #525, control-upgrade has no EXIT floor: a run killed mid-fetch/build leaves 'started' as the final record #535/fix(control): control-upgrade shares control-apply's EXIT floor (#535) #536, fix: surface onion SOCKS setup and advisory proxy diagnostics #548, fix: clean up partial refresh profiler overrides #552, api-refresh stops refreshing the enriched feed after a max_temp_c control-apply (seen twice on the bench rig) #540/perf(api): avoid per-core processes in refresh (#540) #541. Leave[Unreleased]empty.VERSION: change 1.17.4 to 1.18.0.- Commit both on develop, promote to main as the same sha, then tag
v1.18.0from main.
Then:
- pithead re-pins
ARG RIGFORGE_REFto the v1.18.0 commit. - The 2.0.0 soak stands when the diff from the soaked pin is only
CHANGELOG.md,VERSIONand docs. Note thatVERSIONis the version string the appliance reports. - Then 2.0.0 is released.
Until the tag: a RigForge code change that 1.18.0 does not need waits. One it does need means a re-pin and a restarted soak.
This issue tracks the release event only. It closes when v1.18.0 is tagged.
Activity
VijitSingh97 commentedon Oct 3, 2026
Owner note for the release step (2026-10-03): tag v1.18.0 at
f5ff047, not at thedeveloptip.f5ff047is the soaked pin9b05e76(the commit pithead PR #3030 bakes into the 2.0.0 image) plusCHANGELOG.mdandVERSIONonly (Set VERSION 1.18.0 and fold the changelog into [1.18.0] before the pithead 2.0.0 pin #565/release prep: VERSION 1.18.0 and the [1.18.0] changelog (#565) #566). Re-pinning the image to that tag keeps the soak standing, per the 2026-10-02 ruling on pithead#2602.developis taking test-harness merges tonight (test: retain network summary diagnostics and prefix reproduction (#569) #568, Retain bounded diagnostics for intermittent network summary failures #569, fix(tests): fail explicit Stratum auth when input is missing #567, fix(tests): hide contract harness credentials from process arguments #561). A tag at thedeveloptip would put a non-docs diff between the soaked pin and v1.18.0, and that diff restarts the soak.git diff 9b05e76 v1.18.0 --statmust list onlyCHANGELOG.mdandVERSION, plus docs if any.pithead-developer commentedon Oct 4, 2026
2.0.0 re-cut pin (pithead#3116)
Draft PR p2pool-starter-stack/pithead#3117 pins RigForge to current develop tip
b2d4c3d9ca1da74d0e6d5ccce772d401acc8be03, with VERSION1.18.0, per the 2026-10-04 owner ruling on pithead#3116. Tag v1.18.0 at this commit after the soak, subject to the required develop-tip recheck immediately before the pin PR merges. This supersedes the earlierf5ff047tag target for the re-cut.The upstream comparison from the former pin contains only tests, their README and a Makefile test entry; runtime code is unchanged. KVM proof on the new Pithead head is pending. If RigForge develop advances before merge, this comment will be updated to the final tested pin; a runtime change requires the owner's ruling.
VijitSingh97 commentedon Oct 4, 2026
This supersedes the 2026-10-03 07:11Z note above. For the 2.0.0 re-cut, tag v1.18.0 at
b2d4c3d9ca1da74d0e6d5ccce772d401acc8be03, notf5ff047.b2d4c3d, and the soak runs on that image.f5ff047..b2d4c3dis test-only:tests/plus oneMakefileline that adds a test totest-suite.VERSIONreads1.18.0at both commits. Tagging the pinned commit makes the post-soak re-pin a no-op.git diff b2d4c3d <candidate>before tagging anything other thanb2d4c3d.VijitSingh97 commentedon Oct 13, 2026
RigForge v1.18.0 is tagged and released alongside Pithead 2.0.0 (published 2026-10-13); closing this release-pending tracker as done.