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(main): release 1.65.1 #1372

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Apr 12, 2024

🤖 I have created a release beep boop

1.65.1 (2024-04-15)

Bug Fixes


This PR was generated with Release Please. See documentation.

@release-please release-please bot requested a review from a team as a code owner April 12, 2024 18:38
@release-please release-please bot force-pushed the release-please--branches--main--components--api-linter branch 2 times, most recently from ba6d06a to a70a9cf Compare April 12, 2024 21:34
@release-please release-please bot force-pushed the release-please--branches--main--components--api-linter branch from a70a9cf to 8a4c635 Compare April 15, 2024 16:28
@noahdietz noahdietz added the automerge Summon MOG for automerging label Apr 15, 2024
@gcf-merge-on-green gcf-merge-on-green bot merged commit fbdf39d into main Apr 15, 2024
9 checks passed
@gcf-merge-on-green gcf-merge-on-green bot deleted the release-please--branches--main--components--api-linter branch April 15, 2024 16:32
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Summon MOG for automerging label Apr 15, 2024
Copy link
Contributor Author

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.

Fields using proto3 optional incorrectly treated as oneof GLIBC errors
1 participant