$ the-wire · showcase
SQL injection fixed in sqlalchemy-spanner, Gemini SDKs default to v1
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
The day's most consequential change is a security fix in sqlalchemy-spanner, followed by two breaking defaults that landed in the Gemini client libraries and one API-shape change in the interactions types.
fix(sqlalchemy-spanner): prevent SQL injection via JSON key indexing (#18982) googleapis/google-cloud-python
SpannerSQLCompiler._generate_generic_binary was concatenating subscript JSON keys straight into JSON_VALUE(...) SQL strings with no parameterization or escaping. The fix parameterizes those keys and adds unit and MockServer coverage for injection payloads, boundary keys, nested paths, and statement caching, so any code building JSON subscript expressions through the Spanner dialect should move ...
feat!: default Gemini API version to v1 instead of v1beta across SDKs googleapis/python-genai
Gemini Developer API clients now default to v1 instead of v1beta; Vertex AI clients are untouched and still default to v1beta1. Setting GOOGLE_GENAI_API_VERSION=beta restores the previous defaults, which is the shortest path for anyone who depended on beta-only surface.
feat(interactions)!: support multimodal content in CodeExecutionResultStep.result googleapis/python-genai
CodeExecutionResultStep.result used to be a string; it is now the CodeExecutionResultStepResult union of a string or a list of Content items, so code execution can return text and images together. Typed SDK callers reading result as a string must now check which variant is present.
fix: respect configured and default API version for Gemini API file uploads across SDKs googleapis/python-genai
File uploads against the Gemini API now honor the configured and default API version rather than the one the upload path had assumed, which is what makes the v1 default in the change above hold across uploads too.
[Pallas] Validate shard containment and resolve static local offsets in `shard_map` fusion google/jax
In Pallas, _extract_local_block took an unconditional start = 0 shortcut whenever a pulled block dimension matched the local shard size, without checking block_start, so shard_map fusion of outer prologue and epilogue ops could slice the wrong region. The commit adds per-shard containment validation and resolves static local offsets, and this was the bulk of the day's remaining work.
Action items
- → Upgrade sqlalchemy-spanner to a release containing the JSON key parameterization fix (commit c0dba7277) for any code ... googleapis/google-cloud-python [immediate]
- → Set GOOGLE_GENAI_API_VERSION=beta in python-genai deployments that depend on v1beta endpoints, or pin the SDK below t... googleapis/python-genai [plan]
- → Update python-genai call sites that read CodeExecutionResultStep.result as a string to handle the CodeExecutionResult... googleapis/python-genai [plan]