You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bump-release.py: add --force option for stable patch releases #3268
While preparing the v1.37.1 patch release from release-1.37, running hack/bump-release.py reported:
No changes to CPO code or charts detected since v1.37.0. Nothing to release.
The only change since v1.37.0 was the multi-architecture image build fix in #3254. That fix was needed because the v1.37.0 image publishing job failed, so
a new patch release and image tag were required. The version bump in #3255
therefore had to be prepared manually.
What you expected to happen:
The release script should provide an explicit way to prepare a full patch
release when automatic source/chart change detection finds nothing.
How to reproduce it:
Check out a stable release branch with a change that requires new published
images but does not modify cmd/, pkg/, or Helm charts.
Run hack/bump-release.py.
Observe that it exits with Nothing to release.
Anything else we need to know?:
Add a --force option for stable branches. When explicitly supplied, it should
bypass the Nothing to release exit and run the normal full patch-release
flow: bump appVersion, bump all chart versions, and update image references.
The existing confirmation prompt should remain, and the script should clearly
state that release detection was bypassed.
Activity
dlaw4608 commentedon Oct 14, 2026
I will have a PR open soon to close this issue.