fix(deps): update dependency google/cloud-spanner to v2 - autoclosed

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
google/cloud-spanner	^1.97 -> ^2.0

---

Release Notes

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

v2.1.0: google/cloud-spanner v2.1.0

Compare Source

Features

• [Spanner] Add Spanner location API (#​8737) (c6b8e26)
• Add Send and Ack mutations for Queues (c6b8e26)

v2.0.0: google/cloud-spanner v2.0.0

Compare Source

Miscellaneous Chores

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, 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 updates the google/cloud-spanner PHP client library to its latest major version, v2.0 (including v2.1.0). This upgrade ensures the project benefits from the newest features and improvements, such as enhanced Spanner location API support and new queue mutation capabilities, while maintaining compatibility with the updated library.

Highlights

• Dependency Update: The google/cloud-spanner dependency has been updated from version ^1.97 to ^2.0. This is a major version upgrade, incorporating new features introduced in v2.1.0.
• New Features: The updated google/cloud-spanner library now includes the Spanner location API and adds functionality for sending and acknowledging mutations for queues.

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 updates the google/cloud-spanner dependency to version 2. This is a major version upgrade which may introduce breaking changes. My review highlights the risk of breakage due to the lack of corresponding code changes in the samples and the absence of a detailed migration guide in the release notes. Thorough testing is needed to ensure compatibility before merging.

[gemini-code-assist]

This PR updates google/cloud-spanner to v2, a new major version. Major versions often introduce breaking changes. Since there are no corresponding updates in the sample code to adapt to a new API, there is a high risk of the samples breaking. The v2 release notes lack a migration guide, which makes it difficult to assess the impact without running the full test suite.