build: bump version to 1.1.0
CLIENT_VERSION 1000350 -> 1010050. Goes to 1.1.0 rather than 1.0.4 because 1.0.3 is already burned and ambiguous: origin/dragonx's debian changelog already claims 1.0.3 and the daemon bundled in the ObsidianDragon 2.0.1 installer is labelled v1.0.3-dc45e7d90, so a 1.0.4 would sort above builds that contain less. Bumped in configure.ac (authoritative) and in the src/clientversion.h fallback used when HAVE_CONFIG_H is unset, which the header itself asks to be kept in sync. DELIBERATELY NOT BUMPED: SPROUT_VALUE_VERSION, SAPLING_VALUE_VERSION and SAPLING_VALUE_OPTIONAL_VERSION in chain.h. Those are thresholds marking the CLIENT_VERSION that INTRODUCED each block-index format, not "the current version". Raising SAPLING_VALUE_OPTIONAL_VERSION to 1010050 would push every record written by a v1.0.3 node (nVersion 1000350) into the legacy raw-CAmount branch of the deserializer and misparse it. The stale comment naming 1000350 as the current CLIENT_VERSION is updated; the constants stand. 1010050 >= 1000350, so this build still writes and reads the optional format. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
+2
-2
@@ -29,8 +29,8 @@
|
||||
//! These need to be macros, as clientversion.cpp's and bitcoin*-res.rc's voodoo requires it
|
||||
// Must be kept in sync with configure.ac , ugh!
|
||||
#define CLIENT_VERSION_MAJOR 1
|
||||
#define CLIENT_VERSION_MINOR 0
|
||||
#define CLIENT_VERSION_REVISION 3
|
||||
#define CLIENT_VERSION_MINOR 1
|
||||
#define CLIENT_VERSION_REVISION 0
|
||||
#define CLIENT_VERSION_BUILD 50
|
||||
|
||||
//! Set to true for release, false for prerelease or test build
|
||||
|
||||
Reference in New Issue
Block a user