-
### Describe the bug
Any backport PR with merge conflicts will fail CI.
### Steps To Reproduce
Backport a PR that can't be automatically backported (with the `release-2x.xx` label).
### Expect…
-
@matloob requested issue #65264 to be considered for backport to the next 1.21 minor release.
> @gopherbot please backport to Go 1.21 and Go 1.22
-
@matloob requested issue #65264 to be considered for backport to the next 1.22 minor release.
> @gopherbot please backport to Go 1.21 and Go 1.22
-
/cherry-pick 66d8377dbddbf8eb2d692b93e5984bb38fa698e7
-
Discovery ticket for backporting EVM to v0.33 branch https://github.com/onflow/flow-go/tree/v0.33
This issue defines the work needed to get the EVM backported to v0.33 to satisfy partners' integra…
-
Backport from upstream web gui:
- [x] https://github.com/qbittorrent/qBittorrent/pull/19969
- [x] https://github.com/qbittorrent/qBittorrent/pull/19920
- [x] https://github.com/qbittorrent/qBitto…
-
**Is your feature request related to a problem?**
If there is no plan to backport service accounts feature to 2.x, then the code should be removed. Because of this difference, code that touches user …
-
### Description
As mentionned: https://github.com/kumahq/kuma/pull/9479#discussion_r1510967834
-
This is a backport issue for #2521, automatically created via [GitHub Actions workflow](https://github.com/rancher/fleet/actions/runs/9610250371) initiated by @aruiz14
Original issue body:
### Is t…
-
@dmitshur requested issue #68314 to be considered for backport to the next 1.22 minor release.
> @gopherbot Please backport to Go 1.22. Only Go 1.22 needs the fix, as this isn't an issue in Go 1.21.…