-
Notifications
You must be signed in to change notification settings - Fork 807
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
Add generate-release-pr to /hack/release-scripts #1794
Add generate-release-pr to /hack/release-scripts #1794
Conversation
7b35b6e
to
b35fb9c
Compare
/retest |
24a8e7b
to
bddbe0b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
update_readme () { | ||
log "Updating README.md" | ||
# vi macro that adds new driver version 'Container Images' row to README.md | ||
vi -s <(echo "gg/## Container Images |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use sed here for consistency? it would let us remove vi
from the dependencies list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that using sed
is preferable to vi
, but I was not able to figure out a way to use sed
for this operation (after quite some time...).
2. Update CHANGELOG.md | ||
3. Update charts/aws-ebs-csi-driver/CHANGELOG.md" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Idea: It might help to list all the relevant commits that a maintainer has to consider when crafting the CHANGELOG for a particular release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great idea!
I actually showcased a script that does this during a demo a few months ago (and have been using it during releases). I should clean that script up and commit it to our repo, but I think that should be a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found it! Here
b35fb9c
to
51a6d12
Compare
Code Coverage DiffThis PR does not change the code coverage |
51a6d12
to
d58f82f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Is this a bug fix or adding new feature?
Release automation
What is this PR about? / Why do we need it?
This PR adds:
generate-release-pr
in hack/release-scripts: This script prepares (most of) a post-release PR, including updates to:README.md
docs/install.md
Makefile
charts/aws-ebs-csi-driver/Chart.yaml
What testing is done?
Running
./generate-release-pr v1.23.1 v1.24.0
on therelease-1.23
branch will produce the following diff: