Skip to content

fix: rename migration 126 to 121.1#26742

Merged
gantunesr merged 3 commits intodevelopfrom
fix/rename-migration-126-to-121.1
Aug 29, 2024
Merged

fix: rename migration 126 to 121.1#26742
gantunesr merged 3 commits intodevelopfrom
fix/rename-migration-126-to-121.1

Conversation

@montelaidev
Copy link
Copy Markdown
Contributor

@montelaidev montelaidev commented Aug 29, 2024

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.

Open in GitHub Codespaces

Related issues

Related: #26377

Manual testing steps

N/a

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@montelaidev montelaidev added the team-accounts-framework Accounts team label Aug 29, 2024
@montelaidev montelaidev self-assigned this Aug 29, 2024
@montelaidev montelaidev changed the title fix: rename migration of 126 to 121.1 fix: rename migration 126 to 121.1 Aug 29, 2024
@github-actions
Copy link
Copy Markdown
Contributor

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.

@montelaidev montelaidev marked this pull request as ready for review August 29, 2024 12:37
@montelaidev montelaidev requested a review from a team as a code owner August 29, 2024 12:37
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [262dc2e]
Page Load Metrics (1866 ± 93 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint30223591643571274
domContentLoaded15302347184419895
load15392357186619493
domInteractive226737157
Bundle size diffs [🚨 Warning! Bundle size has increased!]
  • background: 12 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@codecov
Copy link
Copy Markdown

codecov bot commented Aug 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.08%. Comparing base (3e5ac65) to head (07c9720).
Report is 3 commits behind head on develop.

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.
📢 Have feedback on the report? Share it here.

@montelaidev montelaidev force-pushed the fix/rename-migration-126-to-121.1 branch from 262dc2e to 753e93c Compare August 29, 2024 15:26
gantunesr
gantunesr previously approved these changes Aug 29, 2024
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [753e93c]
Page Load Metrics (1811 ± 80 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint15262286182118287
domContentLoaded15182132178516479
load15262153181116780
domInteractive137234178
Bundle size diffs [🚨 Warning! Bundle size has increased!]
  • background: 12 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

Copy link
Copy Markdown
Member

@Gudahtt Gudahtt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
@sonarqubecloud
Copy link
Copy Markdown

@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [07c9720]
Page Load Metrics (1705 ± 69 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint15422100170813967
domContentLoaded15352091168414168
load15432101170514469
domInteractive126831136
Bundle size diffs [🚨 Warning! Bundle size has increased!]
  • background: 12 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@gantunesr gantunesr merged commit b9173da into develop Aug 29, 2024
@gantunesr gantunesr deleted the fix/rename-migration-126-to-121.1 branch August 29, 2024 19:09
@github-actions github-actions bot locked and limited conversation to collaborators Aug 29, 2024
@metamaskbot metamaskbot added the release-12.5.0 Issue or pull request that will be included in release 12.5.0 label Aug 29, 2024
@gauthierpetetin gauthierpetetin added release-12.4.0 Issue or pull request that will be included in release 12.4.0 and removed release-12.5.0 Issue or pull request that will be included in release 12.5.0 labels Sep 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-12.4.0 Issue or pull request that will be included in release 12.4.0 team-accounts-framework Accounts team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants