-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: release main #10086
chore: release main #10086
Conversation
30d9033
to
627cdc9
Compare
627cdc9
to
dea354a
Compare
Hm kind of a bummer - the dataplex commits from #10090 aren't present in the release notes....should include:
|
Maybe it's related to the first commit being scoped to dataplex with |
@noahdietz That is the way it has always worked when there are "bundled messages" for a given CL. I am not sure how release-please processes commits like that in general but I assume we could do more post processing on the commit messages to make them show up here. |
dea354a
to
63b9439
Compare
63b9439
to
98949e6
Compare
98949e6
to
63c5b3a
Compare
1cd1e71
to
ca87d5f
Compare
ca87d5f
to
54ba3b4
Compare
Triggered job: cloud-devrel/client-libraries/go/google-cloud-go/release (2024-05-08T19:29:42.728Z) To trigger again, remove the autorelease: triggered label (in a few minutes). |
🤖 I have created a release beep boop
dataplex: 1.16.0
1.16.0 (2024-05-08)
Features
deploy: 1.18.1
1.18.1 (2024-05-08)
Documentation
dlp: 1.13.0
1.13.0 (2024-05-08)
Features
kms: 1.16.0
1.16.0 (2024-05-08)
Features
maps: 1.8.0
1.8.0 (2024-05-08)
Features
This PR was generated with Release Please. See documentation.