8000 chore(main): release 1.11.1 by release-please[bot] · Pull Request #669 · googleapis/python-spanner-sqlalchemy · GitHub
[go: up one dir, main page]
Skip to content
< 8000 div class="gh-header-show ">

chore(main): release 1.11.1 #669

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 27, 2025
Merged

chore(main): release 1.11.1 #669

merged 1 commit into from
May 27, 2025

Conversation

release-please[bot]
Copy link
Contributor

🤖 I have created a release beep boop

1.11.1 (2025-05-27)

Bug Fixes

  • Update README to include isolation level repeatable read (#668) (d84daf6)

This PR was generated with Release Please. See documentation.

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label May 27, 2025
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/python-spanner-sqlalchemy API. label May 27, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label May 27, 2025
@olavloite olavloite merged commit 6ae9bf2 into main May 27, 2025
17 checks passed
@olavloite olavloite deleted the release-please--branches--main branch May 27, 2025 13:24
@release-please Release Please
Copy link
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@olavloite olavloite olavloite approved these changes

Assignees
No one assigned
Labels
api: spanner Issues related to the googleapis/python-spanner-sqlalchemy API. autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@olavloite @yoshi-kokoro
0