[BUG] Migration for cycle_end fails on upgrade #559

New issue

Closed

opened 2026-07-30 09:42:33 +02:00 by simon · 0 comments

simon commented

2026-07-30 09:42:33 +02:00

Owner

After updating to the latest image, the container no longer starts. Migrations abort at 20260630163238_add_cycle_end_to_membership_fee_cycles with an error about "yearly" — looks like something goes wrong with the fee intervals while the new cycle_end column is being filled.

Started happening after #547 was merged.

Expected:

migrations run through on an existing database, and installations can upgrade without manual steps.

After updating to the latest image, the container no longer starts. Migrations abort at `20260630163238_add_cycle_end_to_membership_fee_cycles` with an error about `"yearly"` — looks like something goes wrong with the fee intervals while the new `cycle_end` column is being filled. Started happening after #547 was merged. ## Expected: migrations run through on an existing database, and installations can upgrade without manual steps.

simon added the

bug

label

2026-07-30 09:42:33 +02:00

simon added this to the Sprint 18: Juli 2026 project

2026-07-30 09:42:33 +02:00

simon referenced this issue

2026-07-30 10:34:20 +02:00

Verify Migrations in CI #31

simon referenced this issue from a pull request that will close it,

2026-07-31 09:56:15 +02:00

Fix migration adding the cycle end date to memberships #560