Repository navigation
v1.16.0
gate-110 migration-version-bump
Nextcloud gates both migrations and <post-migration> repair steps on <version> in appinfo/info.xml. A change that adds one without moving the version ships code that reaches no existing instance, silently — occ upgrade says No upgrade required. and exits 0, and occ migrations:status cannot warn you: its Pending Migrations field reads None unconditionally for these apps.
Measured across the fleet before this release: 8 of 21 apps carried 31 stranded steps (decidiq alone had 16). dossiq's RealignStatutoryVocabulary is how corrupted confidentiality values survived on a live instance while the upgrade reported success. All eight are now bumped, and re-measured at zero twice, 26 minutes apart.
The subject is the runnable set, not a directory: a Version<n>Date<n> migration, or any class named in <pre-migration>/<post-migration>. Six of the eight stranded apps ship no lib/Migration/ at all, so a migrations-only check would have caught none of them. <install> steps are excluded (no installed_version to compare on a fresh install), as are traits and helpers.
Delta-scoped on HAVE_DELTA_BASE, so it reddens no branch cut made before it.
Also carries gate-109 seed-required-slugs (#691).
Invariants on this sha: 90 gates each claimed once; acceptance ratchet 241 passed / 0 failed, 83 of 90 fixtured; helper suites 108 passed with 2 documented quarantines.