Skip to content

chore: migrate Spanner to Librarian#13184

Merged
jskeet merged 5 commits intogoogleapis:mainfrom
jskeet:migrate-spanner
Oct 23, 2025
Merged

chore: migrate Spanner to Librarian#13184
jskeet merged 5 commits intogoogleapis:mainfrom
jskeet:migrate-spanner

Conversation

@jskeet
Copy link
Copy Markdown
Contributor

@jskeet jskeet commented Oct 20, 2025

Fixes googleapis/librarian#2422 - see that issue for more details.

Note: this shouldn't be merged until we've done a release with the latest changes from OwlBot (unless we're happy to manually change the next release PR).

After this PR is merged:

  • Generation of API changes will still be automatic, via Librarian instead of OwlBot
  • Releases will be manually initiated: @quartzmo and I will be happy to pair with the Spanner team for the first release or two

I believe the Python team will be working on a similar PR (or multiple ones) this week.

(This commit is just the autogenerated changes; manual changes are in
subsequent commits.)
@jskeet jskeet added do not merge Indicates a pull request not ready for merge, due to either quality or timing. and removed do not merge Indicates a pull request not ready for merge, due to either quality or timing. labels Oct 20, 2025
@jskeet jskeet enabled auto-merge (squash) October 23, 2025 17:20
@jskeet
Copy link
Copy Markdown
Contributor Author

jskeet commented Oct 23, 2025

Set to auto merge - hopefully the Kokoro job iwll pass this time...

@jskeet jskeet merged commit 9a4cb31 into googleapis:main Oct 23, 2025
9 checks passed
@jskeet jskeet deleted the migrate-spanner branch October 23, 2025 17:44
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.

google-cloud-go: migrate Spanner libraries

3 participants