fix: rename migration 126 to 121.1#26742
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [262dc2e]
Page Load Metrics (1866 ± 93 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #26742 +/- ##
========================================
Coverage 70.08% 70.08%
========================================
Files 1414 1414
Lines 49330 49330
Branches 13781 13782 +1
========================================
Hits 34570 34570
Misses 14760 14760 ☔ View full report in Codecov by Sentry. |
262dc2e to
753e93c
Compare
Builds ready [753e93c]
Page Load Metrics (1811 ± 80 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Gudahtt
left a comment
There was a problem hiding this comment.
I found one minor issue, a reference to the old migration number.
Aside from that, this looks good to me! I found a few more problems with the original migration, but I will work on proposing changes in a separate PR. It would be easiest to just re-number things here, adding functional changes would make the git history confusing.
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
|
Builds ready [07c9720]
Page Load Metrics (1705 ± 69 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|



Description
This PR renames migration 126 to 121.1. The reason for this renaming is that commit 759b92e is being cherry-picked into version 12.1.1.
Between version 12.1.1 and the develop branch, there are missing migrations. To avoid skipping these migrations in subsequent releases, we need to rename migration 126 to 121.1.
Related issues
Related: #26377
Manual testing steps
N/a
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist