release(runway): cherry-pick fix(release branch name): cleanup deprecated release branch name cp-13.6.0#37015
Merged
gauthierpetetin merged 1 commit intoOct 21, 2025
Conversation
…ated release branch name cp-13.6.0 (#36991) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** Since we've aligned Extension and Mobile release branch names, we no longer use the deprecated format: `Version-vx.y.z`. The purpose of this PR is to cleanup the repo and remove all traces of the deprecated format for release branch names. Similar changes from github-tools repo can be found in this PR and have been imported: MetaMask/github-tools#146 <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> [](https://codespaces.new/MetaMask/metamask-extension/pull/36991?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: null ## **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. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Standardizes on `release/X.Y.Z` by removing `Version-vX.Y.Z` support across workflows, scripts, and build utils. > > - **CI/Workflows**: > - Restrict triggers and conditions to `release/*` (remove `Version-v*`) in `auto-create-release-pr.yml`, `auto-update-pr-targeting-release.yml`, `check-attributions.yml`, `check-pr-max-lines.yml`, `close-bug-report.yml`, `create-bug-report.yml`, `main.yml`, `publish-prerelease.yml`, `release-pr-approval.yml`, `repository-health-checks.yml`, `tag-release-branch.yml`. > - **Scripts**: > - `scripts/extract-semver.sh`: accept only `release/X.Y.Z`; update error message. > - `scripts/get-next-semver-version.sh`: derive next version from `release/*` branches only. > - `scripts/close-release-bug-report-issue.ts`: extract version only from `release/X.Y.Z`. > - **Build**: > - `development/build/utils.js`: detect release-candidate env only for `release/X.Y.Z` branches. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 33a5309. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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. |
gauthierpetetin
approved these changes
Oct 21, 2025
Collaborator
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Results generated automatically by MetaMask CI |
Collaborator
Builds ready [09bf651]
UI Startup Metrics (1205 ± 54 ms)
|
](https://codespaces.new/MetaMask/metamask-extension/pull/36991?quickstart=1){kind=link}
metamaskbot
added
the
release-13.6.0
Collaborator
|
No release label on PR. Adding release label release-13.6.0 on PR, as PR was cherry-picked in branch 13.6.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Since we've aligned Extension and Mobile release branch names, we no
longer use the deprecated format:
Version-vx.y.z.The purpose of this PR is to cleanup the repo and remove all traces of
the deprecated format for release branch names.
Similar changes from github-tools repo can be found in this PR and have
been imported: MetaMask/github-tools#146
Changelog
CHANGELOG entry: null
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Docs and MetaMask
Extension Coding
Standards.
if applicable
guidelines).
Not required for external contributors.
Pre-merge reviewer checklist
app, test code being changed).
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Note
Drop all support for
Version-vX.Y.Zbranches; onlyrelease/X.Y.Zis recognized across scripts, workflows, and build logic, plus update some GitHub Tools refs.release/*only inauto-create-release-pr.yml,check-attributions.yml,check-pr-max-lines.yml,close-bug-report.yml,create-bug-report.yml,main.yml,publish-prerelease.yml,release-pr-approval.yml,repository-health-checks.yml(changelog checks), andauto-update-pr-targeting-release.yml.tag-release-branch.yml: accept and validate onlyrelease/X.Y.Zbranches.create-release-pr-legacy.ymlandget-release-timelines.ymlto commit3b4244a.....github/scripts/extract-semver.sh: removeVersion-vhandling; requirerelease/X.Y.Z..github/scripts/get-next-semver-version.sh: compute highest version fromrelease/*only..github/scripts/close-release-bug-report-issue.ts: extract version only fromrelease/X.Y.Z.development/build/utils.js: classifyENVIRONMENT.RELEASE_CANDIDATEonly forrelease/X.Y.Zbranches.Written by Cursor Bugbot for commit 09bf651. This will update automatically on new commits. Configure here.
b2534a9