build: bump version to 1.2.0

dev and the v1.1.0 tag were version-indistinguishable: both reported
CLIENT_VERSION 1010050, subversion "/DragonX:1.1.0/" and IS_RELEASE=true, because
660678f9b was the last commit to touch a version file and it predates the tag. The
twenty commits since were therefore invisible to every channel a client can query,
and the in-app updater compares exactly those. Only git-describe distinguished
them, and that degrades to "-unk" on a tarball build.

A minor bump rather than a patch: since v1.1.0 the tree gained auto-shield-coinbase
(a new feature, on by default where the seed is known-recoverable), BIP39 seed
phrases as the default for new wallets, the z_autoshieldstatus RPC, and three new
wallet.dat record types. Understating that as 1.1.1 would hide an on-disk format
change from the one place users look.

The published v1.1.0 tag is left where it is. Re-pointing a tag that is already on
the remote breaks anyone who fetched it.

The wallet feature version deliberately stays at FEATURE_LATEST = 60000. The new
records are additive and older binaries skip unknown types harmlessly, while
bumping it would make them refuse the wallet outright with DB_TOO_NEW. The one real
incompatibility, a truncated hdchain record, is self-healing as of a0ccb4be1, so
refusing to load would be strictly worse for the user than what happens today.

Verified: configure.ac and clientversion.h agree; CLIENT_VERSION 1010050 -> 1020050;
build.sh derives 1.2.0; bitcoin-config.h carries CLIENT_VERSION_MINOR 2 after a
reconfigure run with the depends CONFIG_SITE; a full rebuild of src succeeds with 0
errors and both binaries report v1.2.0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This commit is contained in:

DanS

2026-08-25 21:52:51 +02:00

co-authored by

Claude Opus 5

parent 04ac7c1186

commit 4dc57e80b1

3 changed files with 34 additions and 2 deletions

									
										src/clientversion.h
									
		+1
		-1
	
												View File
												
				@@ -29,7 +29,7 @@

				//! 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 1

				#define CLIENT_VERSION_MINOR 2

				#define CLIENT_VERSION_REVISION 0

				#define CLIENT_VERSION_BUILD 50