-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scripts/release.sh
is not signing off release version bump commits
#18581
Labels
area/tooling
backport/v3.5
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
type/bug
Comments
jmhbnz
added
type/bug
area/tooling
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
labels
Sep 12, 2024
/assign cc @serathius, @ahrtr for your awareness. Let's fix this before our next set of releases. |
@jmhbnz, jfyi, the code is also in the main branch (although there haven't been any recent v3.6 releases, it's affected, too). Ref: Line 157 in f0246a9
And, Lines 118 to 124 in a1375b7
|
Thanks for the catch! |
Closed backport completed in #18599 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/tooling
backport/v3.5
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
type/bug
Bug report criteria
What happened?
For a long time now
scripts/release.sh
has been used on therelease-3.5
branch to automate bumping versions, committing this bump and pushing it to the git remote.Recent examples of these partially-automated commits are:
v3.5.16
v3.5.15
v3.5.14
v3.5.13
v3.5.12
What did you expect to happen?
These commits should be signed off for Developer Certificate of Origin reasons.
How can we reproduce it (as minimally and precisely as possible)?
Produce a release with
scripts/release.sh
on therelease-3.5
branch.Anything else we need to know?
This has not impacted
release-3.4
branch as we have had a historic practice of creating release commits and tags manually on that branch.The relevant section of code is:
etcd/scripts/release.sh
Lines 151 to 159 in 9aaaafe
We should be adding the
--signoff
flag to thegit commit
command.The text was updated successfully, but these errors were encountered: