docs(release): curate the v1.7.126-alpha changelog and What's New entry
create-release.sh builds the frontend at step 4 and validates the curated changelog at step 5, then requires the freshly built bundle to contain the new version. The version reaches the bundle only through the hand-written What's New list, so on a fresh release that check can only pass if the changelog and What's New entries are written BEFORE the script runs. Writing them after is what aborted the first attempt. Leads with the downgrade bug, since that is the one users saw: an Update button offering the release withdrawn for an actively exploited 2FA bypass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
f1b61731ec
commit
1cd068e4f7
@@ -1,6 +1,6 @@
|
||||
[package]
|
||||
name = "archipelago"
|
||||
version = "1.7.125-alpha"
|
||||
version = "1.7.126-alpha"
|
||||
edition = "2021"
|
||||
description = "Archipelago Bitcoin Node OS - Native backend"
|
||||
authors = ["Archipelago Team"]
|
||||
|
||||
Reference in New Issue
Block a user