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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release activerecord-spanner-adapter 1.6.2 #301

Conversation

release-please[bot]
Copy link
Contributor

馃 I have created a release beep boop

1.6.2 (2024-02-19)

Bug Fixes

  • failed to convert active model type to spanner type under certain condition (#299)

This PR was generated with Release Please. See documentation.

@release-please release-please bot requested review from olavloite and a team as code owners February 19, 2024 13:36
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 19, 2024
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/ruby-spanner-activerecord API. label Feb 19, 2024
@olavloite olavloite merged commit 41e3cbe into main Feb 19, 2024
36 checks passed
@olavloite olavloite deleted the release-please--branches--main--components--activerecord-spanner-adapter branch February 19, 2024 14:02
Copy link
Contributor Author

Copy link

Triggered job: cloud-devrel/client-libraries/ruby-spanner-activerecord/release (2024-02-19T14:02:49.315Z)

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/ruby-spanner-activerecord API. autorelease: published kokoro:force-run Add this label to force Kokoro to re-run the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant