Back-merge main into develop after v1.5.0 - #503
Merged
Merged
Conversation
Bump VERSION 1.4.0 -> 1.5.0, move CHANGELOG [Unreleased] -> [1.5.0] (2026-07-13), keep pyproject.toml + uv.lock in lockstep (the #44 drift-guard). v1.5 — the fleet release: consumes RigForge v1.8.0's producer contract (enriched feed + control API). Worker Inspect (#185), energy & profit calculator (#260), enriched-feed chips (#235), the RigForge contract test (#209), Telegram two-way control (#338), on-chain payout confirmation (#381/#462), extra alert sinks (#380), host-side secret merge (#440), plus the late bug/hardening batch (#470/#477/#489/ #493/#499) and the cosign/e2e/box-layout follow-ups. Cut on the build server with `make release` (runs the #54 integration gate against the real nodes incl. a RigForge v1.8.0 rig, builds, stages, smoke-tests, promotes by digest, cosign-signs, and publishes the tag + GitHub Release). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ert fixes Pre-release validation for v1.5.0: - test(tier-4): add a RigForge integration phase to tests/integration/run.sh (--rigforge, wired into e2e.sh when a real rig is borrowed). Against a REAL rigforge v1.8.0 rig it asserts the dashboard consumed the enriched feed live (#235/#260) and Worker Inspect reads it + its write path is fail-closed (#185) — the end-to-end validation the tier-2 contract test (fake) can't give. Runs under the shared-bench flock; self-skips if no rigforge rig is connected; non-destructive. - fix(telegram): render telegram.events.payout_confirmed so the confirmed-payout alert (#381/#462) is actually silenceable (it was on-by-default but unrendered), and list it in the event reference + docs. - docs: complete the telegram.events list in configuration.md (db_reset, block_found, payout_found, payout_confirmed, container_unhealthy) and document the #470 per-operator control-prompt rate limit. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Three harness bugs surfaced while validating v1.5 against a live rigforge-1.8.0 rig on the bench: - backup_stack: `pithead backup -y` refuses to write a plaintext archive unattended (v1.4 hardening) unless PITHEAD_BACKUP_PASSPHRASE is set, so the safety-backup phase aborted the whole run. Pass --no-encrypt — this rollback anchor never leaves the bench, so plaintext is acceptable. - run_harness (targeted): --readiness was handed to the DETACHED run.sh alongside the real phases, but run.sh returns right after readiness, so --auth-fail-closed / --lifecycle / --rigforge silently never ran. Readiness already runs inline first; drop it from the detached phase list. - borrow_miner: only reordered existing pools, assuming a bench pool was already configured. A stock miner has none, so it kept mining to its own pool and 0 workers ever connected. Inject a bench pool (cloned from pool[0] so creds/keepalive carry over) when none matches the bench. With these, `e2e.sh --targeted` borrows a real rig and the RigForge phase (#185/#235/#260) validates the dashboard consuming its live enriched feed: 306 passed / 2 env-skipped / 0 failed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ales (#185) control_worker_apply pinned the worker name with `grep -qE '^[!-~]{1,128}$'`. GNU grep reads the [!-~] range by LOCALE COLLATION, so on any UTF-8-locale host (i.e. every real deployment) it rejects ordinary names like "rig1" with "malformed or missing 'worker' name" — worker config edits were dead on arrival. CI runs under a C/POSIX locale and passed; the release-gate stack suite on a UTF-8 box (gouda) caught it. Force LC_ALL=C so [!-~] is the printable-ASCII byte range, matching the intent and the jq test() checks elsewhere (which are codepoint-based and unaffected). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
release: v1.5.0
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.
Brings the v1.5.0 release line (incl. the #185 UTF-8-locale worker-apply fix and the e2e harness fixes) back into develop, keeping main an ancestor of develop per the release workflow.
🤖 Generated with Claude Code