Skip to content

release: rename changelog branches to release-changelog/${version}#217

Merged
HowardBraham merged 1 commit intomainfrom
rename-changelog
Feb 13, 2026
Merged

release: rename changelog branches to release-changelog/${version}#217
HowardBraham merged 1 commit intomainfrom
rename-changelog

Conversation

@HowardBraham
Copy link
Contributor

@HowardBraham HowardBraham commented Feb 13, 2026

Rename release/${version}-Changelog to release-changelog/${version}


Note

Low Risk
Branch-name and template-formatting changes limited to GitHub release automation scripts; low blast radius but could affect automation if any external tooling still expects the old changelog branch naming.

Overview
Updates release automation to use the new changelog branch naming convention release-changelog/<version> instead of release/<version>-Changelog, including updated detection logic (with a -fallback variant) in update-release-changelog.sh.

Also aligns the release PR template formatting (markdown list/whitespace) and updates the comprehensive test script to use the new changelog branch name.

Written by Cursor Bugbot for commit bcf4d89. This will update automatically on new commits. Configure here.

@HowardBraham HowardBraham requested a review from Gudahtt February 13, 2026 20:55
Copy link
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.

LGTM!

@HowardBraham HowardBraham merged commit 7a3ea83 into main Feb 13, 2026
21 checks passed
@HowardBraham HowardBraham deleted the rename-changelog branch February 13, 2026 22:02
github-merge-queue bot pushed a commit to MetaMask/metamask-extension that referenced this pull request Feb 16, 2026
## **Description**

Fixes three issues we just discovered during the most recent release
cycle:

1. On a changelog branch, like `release/13.19.0-Changelog`, the workflow
ran twice, on both `push` and `pull_request`
   - This was changed to be fixed in MetaMask/github-tools#217
   - Then I simplified `.github/workflows/update-release-changelog.yml`
2. The release branch was not running job `publish-prerelease` because
`needs-benchmarks == 'false'` and the benchmarks were prereqs
3. `prep-e2e` had the gate `if: ${{ (github.head_ref || github.ref_name)
!= 'stable' }}` on the whole job, which prevented it from generating
`test-runs-for-splitting`. Changed to gating just the diff steps.

## **Changelog**

CHANGELOG entry: null

<!--## **Related issues**
## **Manual testing steps**
## **Screenshots/Recordings**
## **Pre-merge author checklist**
## **Pre-merge reviewer checklist**
[skip-e2e]-->



<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Workflow-only changes to CI/release automation; main risk is
accidentally skipping/triggering release jobs due to updated job
conditions and branch filters.
> 
> **Overview**
> Fixes release-cycle GitHub Actions behavior.
> 
> `publish-prerelease` in `main.yml` is now explicitly gated to run when
releases are enabled and **not cancelled**, requiring all non-benchmark
prerequisite jobs to be `success`/`skipped` so benchmarks no longer
block prereleases.
> 
> `prep-e2e.yml` now runs on `stable`, but skips the diff/artifact steps
there so it still produces `test-runs-for-splitting`.
`publish-prerelease.yml` makes downloading `page-load-benchmark-results`
non-blocking (`continue-on-error`). `update-release-changelog.yml` is
simplified by narrowing the push branch filter to semver-like
`release/x.y.z` and removing the extra branch-validation job.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
95b4e36. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants