chore: librarian release pull request: 20251210T223550Z

[rahul2393]

PR created by the Librarian CLI to initialize a release. Merging this PR will auto trigger a release.

Librarian Version: v1.0.0
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-go@sha256:718167d5c23ed389b41f617b3a00ac839bdd938a6bd2d48ae0c2f1fa51ab1c3d

spanner: 1.87.0

1.87.0 (2025-12-10)

Features

• Add Send and Ack mutations for Queues (PiperOrigin-RevId: 832425466) (185951b3)

• Exposing AutoscalingConfig in InstancePartition (PiperOrigin-RevId: 825184314) (185951b3)

• Add Spanner location API (PiperOrigin-RevId: 833474957) (185951b3)

• Add QueryAdvisorResult for query plan (PiperOrigin-RevId: 832425466) (185951b3)

• improve the SQL formatting when printing out SQL (feat(spansql): improve the SQL formatting when printing out SQL #13267) (af0806f4)

• Add grpc.xds.resource_type label to xDS client metrics (feat: Add grpc.xds.resource_type label to xDS client metrics #13358) (b9196cf6)

• support subquery in View Join (feat(spansql): support subquery in View Join #13266) (d19f797b)

Bug Fixes

• add env var to allow disabling directpath bound token (fix(spanner): add env var to allow disabling directpath bound token #13265) (029bc795)

• fix createMultiplexedSession goroutine leak (fix(spanner): fix createMultiplexedSession goroutine leak #13396) (1805e895)

• decoding spanner rows using SelectAll should map values in correct annotations (fix(spanner): decoding spanner rows using SelectAll should map values in correct annotations #13301) (315f65b5)

• error instead of panic for iterator after tx end (fix(spanner): error instead of panic for iterator after tx end #13366) (a27c19ae)

• transaction_tag should be set on BeginTransactionRequest (fix(spanner): transaction_tag should be set on BeginTransactionRequest #13463) (a429aea4)

• Configure keepAlive time for gRPC TCP connections (fix(spanner): Configure keepAlive time for gRPC TCP connections #13216) (ca8f64e0)

• avoid double decrement in session counting (fix(spanner): avoid double decrement in session counting #13395) (e0364214)

Documentation

• minor update for Spanner Location API (PiperOrigin-RevId: 834841888) (185951b3)

• Update description for the BatchCreateSessionsRequest and Session (PiperOrigin-RevId: 832425466) (185951b3)

• Update description for the IsolationLevel (PiperOrigin-RevId: 832425466) (185951b3)

[gemini-code-assist]

Summary of Changes

Hello @rahul2393, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated release initiated by the Librarian CLI, updating the Google Cloud Spanner Go client library to version "1.87.0". Merging this PR will trigger the official release, bringing a suite of new features, important bug fixes, and documentation enhancements to the Spanner client.

Highlights

• Spanner Client Library Update: The Google Cloud Spanner Go client library is being updated to version "1.87.0".
• New Features: This release introduces several new features, including Send and Ack mutations for Queues, exposure of AutoscalingConfig in InstancePartition, a new Spanner location API, QueryAdvisorResult for query plans, improved SQL formatting, xDS client metrics with "grpc.xds.resource_type" label, and support for subqueries in View Joins.
• Bug Fixes: Key bug fixes address issues such as goroutine leaks in "createMultiplexedSession", incorrect row decoding with "SelectAll", panics after transaction end, and ensuring "transaction_tag" is set correctly. It also includes configuration for gRPC TCP keepAlive time and fixes a session counting double decrement.
• Documentation Improvements: Minor documentation updates have been made for the Spanner Location API, "BatchCreateSessionsRequest", "Session", and "IsolationLevel".

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is an automated release for the spanner module, bumping the version to 1.87.0. The changes include updating version numbers in various configuration files and the Go source, and adding a new entry to the changelog. While the version updates are consistent, there's an issue in the spanner/CHANGES.md file where commit links and pull request references are invalid, which will prevent users from tracing the changes. This should be addressed to ensure the changelog is accurate and useful.

[gemini-code-assist]

The commit links and pull request references in this release section appear to be invalid. For example, commit 185951b is referenced for multiple features but does not point to a valid commit in the repository. Similarly, pull request numbers like #13358 do not exist. This makes it difficult for users to track the changes associated with this release.