-
Notifications
You must be signed in to change notification settings - Fork 526
Closed
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.
Milestone
Description
What happened:
- Having headers in
krel release-notesoutput caused the end result of k/k changelog to have duplicated headers. We had to fix this in 1.20 and again in 1.21 after the release. - We also have duplicated
dependenciessection. In 1.21 we handled it in the same PR linked previously, while in 1.20 it was caught later on.
What you expected to happen:
Release notes team need not to manually edit document in k/sig-release before the release
How to reproduce it (as minimally and precisely as possible):
Create a minor release in k/k 😅
Anything else we need to know?:
/assign
/cc pmmalinov01 puerco
Environment:
- Cloud provider or hardware configuration: -
- OS (e.g:
cat /etc/os-release): - - Kernel (e.g.
uname -a): - - Others: -
Metadata
Metadata
Assignees
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.