-
Notifications
You must be signed in to change notification settings - Fork 159
Add changelog for release 1.4.0 #878
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
Conversation
Hi @lizhuqi. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
CHANGELOG/CHANGELOG-1.4.md
Outdated
|
||
### Bug or Regression | ||
|
||
- Upgraded to go1.17 which fixes memory bloat problems. ([#850](https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/850), [@mattcary](https://github.com/mattcary)) |
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.
Hmm, this is already in the 1.3.4 release notes, looks like the autodetect didn't work right, can you remove it? It may cause confusion when figuring out which version has which fix.
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.
Removed in the new commit.
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lizhuqi, mattcary 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 |
/retest |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Release notes for upcoming 1.4.0 release
Which issue(s) this PR fixes:
Fixes #
N/A
Special notes for your reviewer:
Does this PR introduce a user-facing change?: