Skip to content
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

chore(master): release 20.0.0 #1146

Merged
merged 2 commits into from
Mar 10, 2022
Merged

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Feb 9, 2022

🤖 I have created a release beep boop

20.0.0 (2022-03-10)

⚠ BREAKING CHANGES

Features

Bug Fixes

Miscellaneous Chores


This PR was generated with Release Please. See documentation.

@comment-bot-dev
Copy link

comment-bot-dev commented Feb 9, 2022

Thanks for the PR! 🚀
✅ Lint checks have passed.

@release-please release-please bot force-pushed the release-please--branches--master branch from 22dbba7 to bb12841 Compare February 9, 2022 17:41
@bharathkkb
Copy link
Member

@morgante I believe #1142 was breaking due to provider bump

@bharathkkb bharathkkb added the release-please:force-run Force release-please to check for changes. label Feb 24, 2022
@release-please release-please bot removed the release-please:force-run Force release-please to check for changes. label Feb 24, 2022
@release-please release-please bot changed the title chore(master): release 19.1.0 chore(master): release 20.0.0 Feb 24, 2022
@release-please release-please bot force-pushed the release-please--branches--master branch from bb12841 to 48ef67f Compare February 24, 2022 04:39
@bharathkkb
Copy link
Member

hold for #1140

@release-please release-please bot force-pushed the release-please--branches--master branch 2 times, most recently from 2a47783 to 3cb41d2 Compare March 3, 2022 02:14
Copy link
Contributor

@morgante morgante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to do a bit more work before releasing this. In particular, the upgrade guide will need to be enhanced with some more details on how to handle existing GKE clusters w/ ASM installed. It's not sufficient to tell customers they need to abandon their clusters.

@bharathkkb
Copy link
Member

@Monkeyanator mentioned there isn't a straightforward migration path due to the difference in exposed options via CPR API. We could showcase swapping in the new module as a starting point with the caveat of possible workload disruption?

@morgante
Copy link
Contributor

morgante commented Mar 3, 2022

Blocking bug: #1164.

@bharathkkb
Copy link
Member

hold for #1166

@release-please release-please bot force-pushed the release-please--branches--master branch 2 times, most recently from cb26957 to 9154c56 Compare March 8, 2022 22:58
@bharathkkb
Copy link
Member

cleanup #1168 before release

@release-please release-please bot force-pushed the release-please--branches--master branch from 9154c56 to de70e69 Compare March 10, 2022 18:14
@bharathkkb bharathkkb requested a review from morgante March 10, 2022 19:16
@bharathkkb
Copy link
Member

blocking issues have been resolved

@bharathkkb
Copy link
Member

/cc @kaariger

@morgante morgante merged commit 774fc12 into master Mar 10, 2022
@release-please
Copy link
Contributor Author

CPL-markus pushed a commit to WALTER-GROUP/terraform-google-kubernetes-engine that referenced this pull request Jul 15, 2024
* chore(master): release 20.0.0

* Update CHANGELOG.md

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Morgante Pell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants