Make the upgrade from 1.4.0 safe and test every upgrade in CI closes #31 #655
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!655
Loading…
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-31"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #31
Description of the implemented changes
The changes were:
Upgrade to 1.5.0: instances on 1.4.0 upgrade without crash loops, lock-outs or lost settings, and every test run migrates a real 1.4.0 database with its edge cases.
What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
test/fixtures/upgrade/1.4.0.sql, a dump of the real 1.4.0 image pluszoo.sql, about 2,100 lines. The fixture is renewed per release withci/upgrade-fixture.sh.@oddbird/popover-polyfill0.7.3 (BSD-3-Clause) inassets/vendor/. It is bundled always and applies itself only in browsers without popovers.OidcIdentityBackfillmodule: the migration carries its own SQL. CODE_GUIDELINES now says migrations do not call application code.FORCE_SEEDS=truestill forces them).ASSOCIATION_NAMEacts only at first set-up.bin/mv eval.20261110000000_drop_stale_settings_valuescleans values older releases left in the settings row (pure SQL). Its down migration does nothing.ci-dev(about 3 s) in its own database<test db>_upgrade.