mengw15 opened a new issue, #8377: URL: https://github.com/apache/texera/issues/8377
### What happened? `Direct Backport Push` cherry-picks a cleanly-applying fix straight onto the release branch and pushes it. Since `release/*` was brought under the Merge Queue ruleset, every one of those pushes is rejected: ``` remote: error: GH013: Repository rule violations found for refs/heads/release/v1.3. remote: - Changes must be made through the merge queue remote: - Changes must be made through a pull request. remote: - 3 of 3 required status checks are expected. ! [remote rejected] HEAD -> release/v1.3 (push declined due to repository rule violations) ``` It retries five times and fails. Latest occurrence: [run 33706287941](https://github.com/apache/texera/actions/runs/33706287941/job/100496019398) on #8347. The last direct push that succeeded onto `release/v1.2` was 2026-07-24 (`9a989b4bd`). Nothing has landed that way since. The counterintuitive part is that **the cleaner the backport, the more certain it is to be lost**. The conflict path opens a PR and still works — which is why nearly everything that has reached `release/v1.2` in the last six weeks arrived as a backport PR someone finished by hand. It is not silent: the job goes red, a comment lands on the original PR, and a red `backport/<branch>` commit status is set. But the original PR is already merged by then and nobody watches the Actions tab, so it went unnoticed for six weeks. Fixes lost this way — on `main`, not on `release/v1.2`, with nothing tracking them: - #6914 `fix(frontend): raise ng serve heap limit` - #7587 `fix(deps): bump hono` - #7588 `fix(deps): bump js-yaml` - #8110 `fix(frontend): use singular relative time units` - #8293 `fix(amber): declare cloudpickle in LICENSE-binary-python` — the CI license-drift fix itself, so `release/v1.2` still carries that problem ### How to reproduce? 1. Merge a `fix:` PR into `main` carrying a `release/*` label whose cherry-pick applies cleanly onto that branch. 2. Watch `Direct Backport Push` for that push: `Discover direct backport targets` succeeds, then `backport #N to release/vX.Y` fails on `git push` with `GH013`. 3. The fix is on `main` and never reaches the release branch, while the label on the merged PR still says it did. ### Version/Branch main -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
