Skip to content

Commit c83569b

Browse files
committed
edit
1 parent d19b27c commit c83569b

2 files changed

Lines changed: 0 additions & 13 deletions

File tree

.github/scripts/release-branch-sync.sh

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -106,15 +106,6 @@ stable_has_new_commits() {
106106
get_active_release_branches() {
107107
local branches=""
108108

109-
# Query open and draft PRs with title starting with "release:" (case-insensitive)
110-
# The jq filter extracts version from PR titles like "release: 7.36.0" or "Release: 7.36.0 (#1234)"
111-
#
112-
# `--limit` must be high enough that the next release PR is always in the
113-
# result set. The default `gh pr list` limit is 30, which is not enough for
114-
# busy repos (e.g. metamask-extension) where the release PR is often older
115-
# than the 30 most-recently-created open PRs — in that case the script would
116-
# silently log "No active release branches found" and exit without creating
117-
# any sync PR. See https://consensyssoftware.atlassian.net/browse/MCRM-66.
118109
local pr_data
119110
pr_data=$(gh pr list \
120111
--state open \

CHANGELOG.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10-
### Fixed
11-
12-
- Fix `release-branch-sync` action silently skipping the next release PR when the repo has many open PRs. `gh pr list` was called without `--limit` and defaulted to 30 results, so the next release PR could fall outside the returned set. This caused hotfix sync PRs (e.g. `release/13.20.1``release/13.21.0` on metamask-extension) not to be auto-created. Now scans up to 500 open PRs ([MCRM-66](https://consensyssoftware.atlassian.net/browse/MCRM-66)).
13-
1410
## [1.9.2]
1511

1612
### Changed

0 commit comments

Comments
 (0)