Skip to content

fix migrations that are out of sequence between 3.34.2 and 3.35 by moving them to the end of the migration queue.

Administrator requested to merge fix-migration-sequence-alternative into main

Created by: coury-clark

Alternate approach to fix the issue raised in https://github.com/sourcegraph/sourcegraph/pull/29392. This has the advantage that these migrations will be automatically applied after the patch upgrade. I've verified from the Code Insights team that our migration is compatible, and had @courier-new check the batch changes migrations.

Note: we should merge either #29392 or this one, not both

This will resequence the skipped migrations as if they were created now.

Merge request reports

Loading