Skip to content

Commit 7649402

Browse files
VijitSingh97claude
andauthored
release: fold #637 into the 1.9.0 changelog section (#648)
Same bookkeeping as #645 for the last rolled-in PR (#647): the entry moves from Unreleased into the section v1.9.0 actually ships. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
1 parent a930dec commit 7649402

1 file changed

Lines changed: 8 additions & 10 deletions

File tree

CHANGELOG.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,6 @@ per the process in [`docs/releasing.md`](docs/releasing.md).
1111

1212
## [Unreleased]
1313

14-
### Added
15-
16-
- **One-click upgrade names its restore point (#637).** Before an in-place upgrade overwrites
17-
the running install, the runner copies `config.json` and the rendered `.env` to timestamped
18-
`.bak-upgrade-*` siblings — and refuses to proceed if it cannot; a failure during the
19-
upgrade names those copies in the result and the dashboard modal. On the versioned layout
20-
the result (and the "Upgraded" modal) names the previous version dir — the rollback copy
21-
#629 already kept but never pointed at. The copies are written symlink-safely (mktemp +
22-
rename, the #629 co-tenant threat model) and pruned to the newest three pairs.
23-
2414
## [1.9.0] - 2026-07-18
2515

2616
**Stratum link security.** v1.9 locks the last cleartext link — miner ↔ stack
@@ -33,6 +23,14 @@ steady-state CPU cost drops via healthcheck and peer-count tuning (#595).
3323

3424
### Added
3525

26+
- **One-click upgrade names its restore point (#637).** Before an in-place upgrade overwrites
27+
the running install, the runner copies `config.json` and the rendered `.env` to timestamped
28+
`.bak-upgrade-*` siblings — and refuses to proceed if it cannot; a failure during the
29+
upgrade names those copies in the result and the dashboard modal. On the versioned layout
30+
the result (and the "Upgraded" modal) names the previous version dir — the rollback copy
31+
#629 already kept but never pointed at. The copies are written symlink-safely (mktemp +
32+
rename, the #629 co-tenant threat model) and pruned to the newest three pairs.
33+
3634
- **XvB raffle wins on the chart and in a log (#644).** The dashboard reads XvB's public winners
3735
log (over Tor, about every 30 minutes) and records every round your wallet won. Wins show as
3836
gold stars on the hashrate chart (hover for the round type and credited hashrate), as a

0 commit comments

Comments
 (0)