Skip to content

Conversation

@metamaskbot
Copy link
Collaborator

Version Bump After Release

This PR bumps the main branch version from 13.1.0 to 13.2.0 after cutting the release branch.

Why this is needed:

  • Nightly builds: Each nightly build needs to be one minor version ahead of the current release candidate
  • Version conflicts: Prevents conflicts between nightlies and release candidates
  • Platform alignment: Maintains version alignment between MetaMask mobile and extension
  • Update systems: Ensures nightlies are accepted by app stores and browser update systems

What changed:

  • Version bumped from 13.1.0 to 13.2.0
  • Platform: extension
  • Files updated by set-semvar-version.sh script

Next steps:

This PR should be manually reviewed and merged by the release manager to maintain proper version flow.

Related:

  • Release version: 13.1.0
  • Release branch: Version-v13.1.0
  • Platform: extension
  • Test mode: false

This PR was automatically created by the create-platform-release-pr.sh script.

This automated version bump ensures that:
- main branch version is ahead of the release branch
- Future nightly builds will have correct versioning

Release version: 13.1.0
New main version: 13.2.0
Platform: extension
@metamaskbot metamaskbot added the team-bots Bot team (for MetaMask Bot, Runway Bot, etc.) label Aug 4, 2025
@gauthierpetetin gauthierpetetin marked this pull request as ready for review August 4, 2025 17:52
@metamaskbot
Copy link
Collaborator Author

Builds ready [27bba0b]
UI Startup Metrics (1146 ± 70 ms)
PlatformBuildTypePageMetricMean (ms)Min (ms)Max (ms)Std Dev (ms)P 75 (ms)P 95 (ms)
ChromeBrowserifyHomeuiStartup1146100613667011881284
load97186411406310181104
domContentLoaded96485911196210101099
domInteractive17147471631
firstPaint65012811233919941081
backgroundConnect21420025810219234
firstReactRender19154251930
getState114140141025
initialActions30516213
loadScripts75765491062806878
setupStore64162710
WebpackHomeuiStartup22411677270322623832574
load16711212198317917761900
domContentLoaded16641209197617817721888
domInteractive181190151452
firstPaint1756150674184318
backgroundConnect3113332343256
firstReactRender21494421117372394
getState2742996313260
initialActions7217017616
loadScripts16601206196417617691882
setupStore3362987016282
FirefoxBrowserifyHomeuiStartup1296113516009513601452
load111499112847411721248
domContentLoaded111499012837411721247
domInteractive993429651100247
firstPaintNaNNaNNaNNaNNaNNaN
backgroundConnect261594132757
firstReactRender25205692351
getState7213415627
initialActions30447212
loadScripts109397212707511461231
setupStore939213743
WebpackHomeuiStartup15781346195812216191818
load1316113915959813871504
domContentLoaded1316113915949813861504
domInteractive95302714597234
firstPaintNaNNaNNaNNaNNaNNaN
backgroundConnect3117107153264
firstReactRender52429895466
getState83468826
initialActions5017718313
loadScripts1292112115729713481483
setupStore9413514732
Benchmark value 215 exceeds gate value 10 for chrome browserify home mean backgroundConnect
Benchmark value 3 exceeds gate value 1 for chrome browserify home mean initialActions
Benchmark value 234 exceeds gate value 18 for chrome browserify home p95 backgroundConnect
Benchmark value 13 exceeds gate value 1.2 for chrome browserify home p95 initialActions
Benchmark value 2242 exceeds gate value 2192 for chrome webpack home mean uiStartup
Benchmark value 33 exceeds gate value 32 for chrome webpack home mean setupStore
Benchmark value 2575 exceeds gate value 2454 for chrome webpack home p95 uiStartup
Benchmark value 394 exceeds gate value 370 for chrome webpack home p95 firstReactRender
Benchmark value 260 exceeds gate value 195 for chrome webpack home p95 getState
Benchmark value 16 exceeds gate value 7 for chrome webpack home p95 initialActions
Benchmark value 282 exceeds gate value 65 for chrome webpack home p95 setupStore
Benchmark value 27 exceeds gate value 25 for firefox browserify home mean backgroundConnect
Benchmark value 4 exceeds gate value 1 for firefox browserify home mean initialActions
Benchmark value 10 exceeds gate value 9 for firefox browserify home mean setupStore
Benchmark value 247 exceeds gate value 195 for firefox browserify home p95 domInteractive
Benchmark value 27 exceeds gate value 24 for firefox browserify home p95 getState
Benchmark value 12 exceeds gate value 2 for firefox browserify home p95 initialActions
Benchmark value 43 exceeds gate value 27 for firefox browserify home p95 setupStore
Benchmark value 31 exceeds gate value 26 for firefox webpack home mean backgroundConnect
Benchmark value 52 exceeds gate value 38 for firefox webpack home mean firstReactRender
Benchmark value 5 exceeds gate value 1 for firefox webpack home mean initialActions
Benchmark value 234 exceeds gate value 156 for firefox webpack home p95 domInteractive
Benchmark value 64 exceeds gate value 49 for firefox webpack home p95 backgroundConnect
Benchmark value 66 exceeds gate value 50 for firefox webpack home p95 firstReactRender
Benchmark value 13 exceeds gate value 2 for firefox webpack home p95 initialActions
Benchmark value 32 exceeds gate value 28 for firefox webpack home p95 setupStore
Sum of mean exceeds: 287ms | Sum of p95 exceeds: 868.8ms
Sum of all benchmark exceeds: 1155.8ms

Bundle size diffs [🚨 Warning! Bundle size has increased!]
  • background: 43 Bytes (0%)
  • ui: 0 Bytes (0%)
  • common: 10 Bytes (0%)

@gauthierpetetin gauthierpetetin changed the title Bump main version to 13.2.0 chore: Bump main version to 13.2.0 Aug 4, 2025
@HowardBraham HowardBraham added this pull request to the merge queue Aug 4, 2025
Merged via the queue into main with commit faf3144 Aug 4, 2025
280 of 284 checks passed
@HowardBraham HowardBraham deleted the version-bump/13.2.0 branch August 4, 2025 21:20
@gauthierpetetin gauthierpetetin self-assigned this Aug 5, 2025
github-merge-queue bot pushed a commit that referenced this pull request Aug 11, 2025
…er version (#34855)

## **Description**

package.json can no longer be used to craft next semver version with our
new process, as it's now bumped to the next version number by a version
bump PR such as this one:
#34840

We need to stop relying on package.json when crafting next semver
version otherwise, the automatic labeling of PRs and linked issues gets
inaccurate.

Same PR for Mobile:
MetaMask/metamask-mobile#17822

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/34855?quickstart=1)

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry:

## **Related issues**

Fixes:

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **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.
mcmire pushed a commit that referenced this pull request Aug 11, 2025
## Version Bump After Release

This PR bumps the main branch version from 13.1.0 to 13.2.0 after
cutting the release branch.

### Why this is needed:
- **Nightly builds**: Each nightly build needs to be one minor version
ahead of the current release candidate
- **Version conflicts**: Prevents conflicts between nightlies and
release candidates
- **Platform alignment**: Maintains version alignment between MetaMask
mobile and extension
- **Update systems**: Ensures nightlies are accepted by app stores and
browser update systems

### What changed:
- Version bumped from `13.1.0` to `13.2.0`
- Platform: `extension`
- Files updated by `set-semvar-version.sh` script

### Next steps:
This PR should be **manually reviewed and merged by the release
manager** to maintain proper version flow.

### Related:
- Release version: 13.1.0
- Release branch: Version-v13.1.0
- Platform: extension
- Test mode: false

---
*This PR was automatically created by the
`create-platform-release-pr.sh` script.*

Co-authored-by: [email protected] <[email protected]>
@gauthierpetetin gauthierpetetin added release-13.2.0 Issue or pull request that will be included in release 13.2.0 and removed release-13.3.0 labels Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

extension-delivery release-13.2.0 Issue or pull request that will be included in release 13.2.0 team-bots Bot team (for MetaMask Bot, Runway Bot, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants