ci(sqlalchemy-spanner): add compliance tests against emulator - #17906
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
sakthivelmanii
force-pushed
the
feat-sqlalchemy-spanner-emulator-workflow
branch
from
July 27, 2026 13:29
1c07457 to
98b8cbc
Compare
olavloite
approved these changes
Jul 27, 2026
|
|
||
| services: | ||
| emulator: | ||
| image: gcr.io/cloud-spanner-emulator/emulator:latest # zizmor: ignore[unpinned-images] |
Contributor
There was a problem hiding this comment.
Thank you for this tip! I was already quite annoyed by the fact that I had to pin the Emulator version for some other repos....
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕