-
### What would you like to be added?
Backport all the failpoint comments from main branch to release-3.4 and release-3.5.
For example compactBeforeSetFinishedCompact from https://github.com/etcd-io…
-
This is a backport issue for #11993, automatically created via [GitHub Actions workflow](https://github.com/rancher/dashboard/actions/runs/11018657458) initiated by @richard-cox
Original issue body:…
-
**Describe the bug**
When running the ProjectTracker sample in the current `v8.x` branch, WebAssembly code fails because it can't find the Backport.System.Threading.Lock package.
![image](https://…
-
ideally make it optional, but the fact that discord sat on their asses for ~~4~~ 5 years on this feature shouldn't be our problem
-
https://github.com/Azure/hyperlocal-windows
-
If it's possible that would be great!
-
### Context
Right now, backporting PRs is a manual process that is done by engineers. This is problematic since:
* it is prone to error since engineers may forget to backport a PR. This has result…
-
Go to [the Golang group](https://groups.google.com/g/golang-announce) to view the announcement.
Follow the on-call runbook to backport fixes to all supported Golang versions.
-
This is for testing backport
-
### Is your feature request related to a problem? Please describe
The backport fails for most PR due to conflicts on CHANGELOG.md. I am wondering if there is better way around this.
### Describe the…