Emergency hotfix release process — cherry-pick patch releases
Open
area/pipeline
engineering item
engsys
release-activity
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
## Problem
Today we don't have an automated way to do a true emergency patch release. When a breaking change or critical bug ships, the next release includes everything merged to main — new features, refactors, etc. — increasing blast radius instead of limiting it.
The team wants the ability to cherry-pick specific commit(s) on top of an existing release tag and push a new patch release from it.
Contributor guide
Assessment
This issue has not been assessed yet.