17 lines
1.7 KiB
Plaintext
17 lines
1.7 KiB
Plaintext
# migration_version application_rollback_policy reason
|
|
20260722110837 forward_only hidden requests can store no coordinates and old code requires a point
|
|
20260722123052 application_safe additive partial geography index
|
|
20260722190604 forward_only assignment history permits rows the old single-assignment model cannot interpret safely
|
|
20260723015032 application_safe additive request-helper lookup index
|
|
20260724161628 application_safe additive support conversation and status-history tables
|
|
20260731230828 forward_only pending support verification status is not understood by older releases
|
|
20260801002933 forward_only staff roles move out of the removed users.role column into role assignments
|
|
20260801123806 application_safe additive concurrent user directory search indexes
|
|
20260801141743 application_safe additive concurrent operations queue search indexes
|
|
20260801200302 application_safe additive generated public discovery coordinate columns
|
|
20260812120611 application_safe dropping the delivery-channel check allows inbox-only subscriptions that old code can still read safely
|
|
20260813194249 application_safe additive nullable inbound-provider identity columns and a partial unique index are ignored by the previous application
|
|
20260827173037 application_safe additive discovery rollup tables and maintenance triggers are ignored by the previous application while continuing to follow its writes
|
|
20260827180241 forward_only pending lifecycle uniqueness can reject duplicate account access or deletion requests that the previous application may still attempt to insert
|
|
20260827225430 application_safe replacing rollup trigger functions preserves the existing schema and application contract while serializing concurrent counter inserts
|