test: add upgrade home fixture coverage

This commit is contained in:
Eric Wendland 2026-07-05 23:40:39 +02:00
commit 3fbd64f131
3 changed files with 120 additions and 4 deletions

View file

@ -34,6 +34,19 @@ After the first deployment tag:
- Signed operation formats must not be changed without a new version or
explicit migration behavior.
## Upgrade And Rollback
Before the first deployment tag, upgrade tests use synthetic pre-release homes
that exercise the same on-disk contracts as tagged fixtures: config, SQLite
schema, signed keychain/auth logs, CAS metadata, and peer-card metadata. Once a
tagged pre-release exists, its fixture home must be kept and migrated by the
current test suite.
Store migrations are forward-only. A newer daemon may upgrade `geth.sqlite` in
place, so rollback means restoring a backup made before the upgrade or using a
copied fixture home. Downgrading a migrated home with an older binary is not a
supported recovery path unless a release note explicitly says so.
## Security Updates
Security fixes should be released as soon as practical after validation. The