Skip to content

chore(main): release 2.17.0 #1580

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

Merged
merged 1 commit into from
Apr 21, 2024
Merged

Conversation

release-please[bot]
Copy link
Contributor

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

🤖 I have created a release beep boop

2.17.0 (2024-04-21)

Features


This PR was generated with Release Please. See documentation.

@release-please release-please bot requested review from a team as code owners April 21, 2024 07:36
@product-auto-label product-auto-label bot added size: s Pull request size is small. api: spanner Issues related to the googleapis/java-spanner-jdbc API. labels Apr 21, 2024
@olavloite olavloite added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Apr 21, 2024
@release-please release-please bot force-pushed the release-please--branches--main branch 2 times, most recently from 063f15a to 66886e4 Compare April 21, 2024 07:58
@release-please release-please bot force-pushed the release-please--branches--main branch from 66886e4 to 6e36c7d Compare April 21, 2024 07:58
@olavloite olavloite removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Apr 21, 2024
@olavloite olavloite added the automerge Merge the pull request once unit tests and other checks pass. label Apr 21, 2024
Copy link

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Apr 21, 2024
@olavloite olavloite added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Apr 21, 2024
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Apr 21, 2024
@olavloite olavloite added the automerge Merge the pull request once unit tests and other checks pass. label Apr 21, 2024
@gcf-merge-on-green gcf-merge-on-green bot merged commit 40e4da6 into main Apr 21, 2024
@gcf-merge-on-green gcf-merge-on-green bot deleted the release-please--branches--main branch April 21, 2024 22:00
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Apr 21, 2024
Copy link
Contributor Author

Copy link

Triggered job: cloud-devrel/client-libraries/java/java-spanner-jdbc/release/stage (2024-04-21T22:00:55.005Z)

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
Labels
api: spanner Issues related to the googleapis/java-spanner-jdbc API. autorelease: published size: s Pull request size is small.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants