Skip to content

chore(deps): update dependency google-cloud-spanner to v3.65.0#175

Open
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit intomainfrom
konflux/mintmaker/main/google-cloud-spanner-3.x
Open

chore(deps): update dependency google-cloud-spanner to v3.65.0#175
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit intomainfrom
konflux/mintmaker/main/google-cloud-spanner-3.x

Conversation

@red-hat-konflux-kflux-prd-rh02
Copy link
Copy Markdown
Contributor

@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot commented Apr 29, 2026

This PR contains the following updates:

Package Change Age Confidence
google-cloud-spanner (source) ==3.63.0==3.65.0 age confidence

Release Notes

googleapis/google-cloud-python (google-cloud-spanner)

v3.65.0: google-cloud-spanner: v3.65.0

Compare Source

v3.65.0 (2026-04-13)

v3.64.0: google-cloud-spanner: v3.64.0

Compare Source

Features
  • use inline begin to eliminate BeginTransaction RPC (#​1502) (00d5f8e6)

  • add TLS/mTLS support for experimental host (#​1479) (0c4c5da3)

  • add Client Context support to options (#​1499) (0da5f785)

  • Exposing total CPU related fields in AutoscalingConfig (PiperOrigin-RevId: 8458193) (9d2338a6)

  • include cache updates into the ResultSet response (PiperOrigin-RevId: 8655460) (9d2338a6)

  • add a ClientContext field to Spanner requests (PiperOrigin-RevId: 8533230) (9d2338a6)

  • include cache updates and routing hint into BeginTransaction and Commit request/response respectively (PiperOrigin-RevId: 8780198) (9d2338a6)

  • add Secure Parameters to the ClientContext (PiperOrigin-RevId: 8533230) (9d2338a6)

  • implement native asyncio support via Cross-Sync (#​1509) (f822fd7c)

Bug Fixes
  • add threading import and _resource_info to snapshot.py (659034aa)

  • restore implicit database_dialect reload in sync client (#​1537) (67f51043)

  • resolve async deadlock in multiplexed session manager (#​1520) (c8f936b0)

Documentation
  • mark new AsyncIO APIs as experimental (#​1533) (3909c045)

  • A comment for field transaction_tag in message .google.spanner.v1.RequestOptions is changed (PiperOrigin-RevId: 8655460) (9d2338a6)

  • A comment for field routing_hint in messages .google.spanner.v1.ResultSet and .google.spanner.v1.PartialResultSet are changed (PiperOrigin-RevId: 8780198) (9d2338a6)

  • Update high_priority_cpu_utilization_percent in AutoscalingConfig to be Optional and clarify its behavior when not specified (PiperOrigin-RevId: 8458193) (9d2338a6)

  • A comment for field params in message .google.spanner.v1.PartitionQueryRequest is changed (PiperOrigin-RevId: 8655460) (9d2338a6)

  • A comment in message .google.spanner.v1.TransactionOptions.ReadWrite.ReadLockMode is changed (PiperOrigin-RevId: 8780198) (9d2338a6)

  • A comment for field commit_timestamp in message .google.spanner.v1.BatchWriteResponse is changed (PiperOrigin-RevId: 8655460) (9d2338a6)

  • minor update for Spanner Location API (PiperOrigin-RevId: 8348418) (9d2338a6)

  • A comment for field param_types in message .google.spanner.v1.PartitionQueryRequest is changed (PiperOrigin-RevId: 8655460) (9d2338a6)


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants