chore: librarian release pull request: 20260210T184655Z

[tswast]

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

Librarian Version: v0.8.0
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:1a2a85ab507aea26d787c06cc7979decb117164c81dd78a745982dfda80d4f68

bigquery-magics: 0.12.0

0.12.0 (2026-02-10)

Features

• support schema view (feat: support schema view #211) (8e1883ee)

• remove bqsql magic to make that name available for bigframes (feat: remove bqsql magic to make that name available for bigframes #210) (c46c94af)

Bug Fixes

• reduce conflicts between Spanner and BigQuery graph visualization on Colab (fix: reduce conflicts between Spanner and BigQuery graph visualization on Colab #209) (7dca7b13)

[gemini-code-assist]

Summary of Changes

Hello @tswast, 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 initiates the release process for version 0.12.0 of the bigquery-magics library. It incorporates several new features, such as schema view support and the removal of the bqsql magic, alongside a critical bug fix addressing visualization conflicts on Colab. Merging this PR will automatically trigger the release.

Highlights

• Features: Added support for schema view.
• Features: Removed the bqsql magic to free up the name for BigFrames.
• Bug Fixes: Reduced conflicts between Spanner and BigQuery graph visualization on Colab.

Changelog

• .librarian/state.yaml
  • Updated the bigquery-magics library version from 0.11.0 to 0.12.0.
• CHANGELOG.md
  • Appended release notes for version 0.12.0, detailing new features and bug fixes.
• bigquery_magics/version.py
  • Incremented the __version__ string from 0.11.0 to 0.12.0.

Activity

• The pull request was automatically created by the Librarian CLI to prepare for a new release.
• Merging this PR is configured to automatically trigger the release process.

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 version of bigquery-magics from 0.11.0 to 0.12.0 across the .librarian/state.yaml, CHANGELOG.md, and bigquery_magics/version.py files. These changes are consistent with a routine release process and correctly reflect the new version number and associated changelog entries. No further action is required.