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 8.0.0 #268

Merged
merged 1 commit into from
Jan 11, 2023
Merged

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Oct 19, 2022

🤖 I have created a release beep boop

8.0.0 (2022-12-29)

⚠ BREAKING CHANGES

  • Add support of "ipv6_access_config" param for compute instance and instance template (#284)
  • support health check logging (#283)
  • Allow setting predictive method for CPU utilization scaling (#255)

Features

  • Add support of "ipv6_access_config" param for compute instance and instance template (#284) (fc40db1)
  • Allow setting predictive method for CPU utilization scaling (#255) (28c77b5)
  • support health check logging (#283) (2b31071)

Bug Fixes

  • fixes lint issues and generates metadata (#288) (b071db1)

This PR was generated with Release Please. See documentation.

@release-please release-please bot force-pushed the release-please--branches--master branch from 541dd5c to f7f31b5 Compare October 19, 2022 22:08
@release-please release-please bot force-pushed the release-please--branches--master branch 3 times, most recently from d763626 to cf2e323 Compare October 28, 2022 18:19
@release-please release-please bot force-pushed the release-please--branches--master branch 2 times, most recently from a51ad14 to 67b793f Compare November 10, 2022 20:13
@release-please release-please bot force-pushed the release-please--branches--master branch from 67b793f to 4d36f00 Compare November 18, 2022 16:07
@release-please release-please bot force-pushed the release-please--branches--master branch from 4d36f00 to f1605d9 Compare November 28, 2022 23:07
@release-please release-please bot requested a review from a team as a code owner November 28, 2022 23:07
@release-please release-please bot force-pushed the release-please--branches--master branch from f1605d9 to 659bbdc Compare November 29, 2022 02:02
@legal90
Copy link
Contributor

legal90 commented Nov 30, 2022

@release-please release-please bot force-pushed the release-please--branches--master branch 3 times, most recently from 9620895 to 8ed0586 Compare December 2, 2022 00:55
@release-please release-please bot force-pushed the release-please--branches--master branch from 8ed0586 to ac7e439 Compare December 12, 2022 17:59
@release-please release-please bot force-pushed the release-please--branches--master branch 3 times, most recently from ca98760 to 7f9e29f Compare December 29, 2022 16:15
@apeabody apeabody added the release-please:force-run Force release-please to check for changes. label Dec 29, 2022
@release-please release-please bot removed the release-please:force-run Force release-please to check for changes. label Dec 29, 2022
@release-please release-please bot force-pushed the release-please--branches--master branch from 7f9e29f to 5d0946f Compare December 29, 2022 23:28
@comment-bot-dev
Copy link

@release-please[bot]
Thanks for the PR! 🚀
✅ Lint checks have passed.

@apeabody apeabody merged commit 01f273d into master Jan 11, 2023
@apeabody apeabody deleted the release-please--branches--master branch January 11, 2023 16:42
@release-please
Copy link
Contributor Author

@legal90
Copy link
Contributor

legal90 commented Jan 11, 2023

Thank you for releasing, @apeabody !

P.S.
Although, the changelog doesn't mention #251, but it was merged in master and is included in tag v8.0.0 🤔

@apeabody
Copy link
Contributor

apeabody commented Jan 11, 2023

Thank you for releasing, @apeabody !

P.S. Although, the changelog doesn't mention #251, but it was merged in master and is included in tag v8.0.0 🤔

Thanks for the note @legal90 - That is curious, we'll need to investigate why it wasn't noted by release-please.

@bharathkkb - I'm wondering if this might have occurred because of the placement of the !. If so, the conventionalcommits check should catch in the future.

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