fix(release branch name): cleanup deprecated release branch name#146
Merged
Conversation
7 tasks
chloeYue
approved these changes
Oct 20, 2025
Qbandev
approved these changes
Oct 20, 2025
github-merge-queue Bot
pushed a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
…3.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 -->
github-merge-queue Bot
pushed a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
…3.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 -->
github-merge-queue Bot
pushed a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
…3.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 -->
runway-github Bot
added a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
](https://codespaces.new/MetaMask/metamask-extension/pull/36991?quickstart=1){kind=link}
… 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 -->
runway-github Bot
added a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
… 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 -->
runway-github Bot
pushed a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
…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 -->
7 tasks
gauthierpetetin
added a commit
to MetaMask/metamask-extension
that referenced
this pull request
Oct 21, 2025
…ated release branch name cp-13.6.0 (#37015) - fix(release branch name): cleanup deprecated 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] > Drop all support for `Version-vX.Y.Z` branches; only `release/X.Y.Z` is recognized across scripts, workflows, and build logic, plus update some GitHub Tools refs. > > - **CI/Workflows**: > - Narrow triggers/conditions to `release/*` only in `auto-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), and `auto-update-pr-targeting-release.yml`. > - `tag-release-branch.yml`: accept and validate only `release/X.Y.Z` branches. > - Update GitHub Tools refs in `create-release-pr-legacy.yml` and `get-release-timelines.yml` to commit `3b4244a...`. > - **Scripts**: > - `.github/scripts/extract-semver.sh`: remove `Version-v` handling; require `release/X.Y.Z`. > - `.github/scripts/get-next-semver-version.sh`: compute highest version from `release/*` only. > - `.github/scripts/close-release-bug-report-issue.ts`: extract version only from `release/X.Y.Z`. > - **Build**: > - `development/build/utils.js`: classify `ENVIRONMENT.RELEASE_CANDIDATE` only for `release/X.Y.Z` branches. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 09bf651. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> [b2534a9](b2534a9) Co-authored-by: Gauthier Petetin <gauthierpetetin@hotmail.com>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
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.
Note
Switch all scripts and tests to use release/{version} branches and "release: {version}" titles, removing legacy Version-v handling.
create-platform-release-pr.sh: Only treatsprevious_version_refas a branch if it matchesrelease/x.y.z(dropsVersion-vx.y.z).get-release-timelines.sh: Userelease/${VERSION}for--headand expect PR titlerelease: ${VERSION}.slack-release-testing.mjs: RemovegetReleaseBranchName; directly query PRs forrelease/${version}.tests/test-create-platform-release-pr-full.sh: Update inputs to userelease/{version}for release and bump PRs.Written by Cursor Bugbot for commit e5e7091. This will update automatically on new commits. Configure here.