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 google-cloud-discovery_engine 0.7.0 #26014

Conversation

release-please[bot]
Copy link
Contributor

🤖 I have created a release beep boop

0.7.0 (2024-05-31)

Features

  • Add control service APIs
  • Promote answer APIs to v1 GA
  • Promote grounding check APIs to v1 GA
  • Promote ranking APIs to v1 GA
  • Promote various APIs to v1 GA (#25965)
  • Support cancelling import operations
  • Support writing user events for blended engines

This PR was generated with Release Please. See documentation.

@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels May 31, 2024
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label May 31, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label May 31, 2024
@aandreassa aandreassa merged commit 0ed0c6b into main May 31, 2024
14 checks passed
@aandreassa aandreassa deleted the release-please--branches--main--components--google-cloud-discovery_engine branch May 31, 2024 00:48
Copy link
Contributor Author

Copy link

Triggered job: cloud-devrel/client-libraries/google-cloud-ruby/release (2024-05-31T00:48:44.185Z)

To trigger again, remove the autorelease: triggered label (in a few minutes).

The release build has started, the log can be viewed here. 🌻

🥚 You hatched a release! The release build finished successfully! 💜

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.

2 participants