Bump google-cloud-bigquery from 3.29.0 to 3.31.0

[dependabot]

Bumps google-cloud-bigquery from 3.29.0 to 3.31.0.

Release notes

Sourced from google-cloud-bigquery's releases.

v3.31.0

3.31.0 (2025-03-20)

Features

• Add query text and total bytes processed to RowIterator (#2140) (2d5f932)
• Add support for Python 3.13 (0842aa1)

Bug Fixes

• Adding property setter for table constraints, #1990 (#2092) (f8572dd)
• Allow protobuf 6.x (0842aa1)
• Avoid "Unable to determine type" warning with JSON columns in to_dataframe (#1876) (968020d)
• Remove setup.cfg configuration for creating universal wheels (#2146) (d7f7685)

Dependencies

• Remove Python 3.7 and 3.8 as supported runtimes (#2133) (fb7de39)

v3.30.0

3.30.0 (2025-02-26)

Features

• Add roundingmode enum, wiring, and tests (#2121) (3a48948)
• Adds foreign_type_info attribute to table class and adds unit tests. (#2126) (2c19681)
• Support resource_tags for table (#2093) (d4070ca)

Bug Fixes

• Avoid blocking in download thread when using BQ Storage API (#2034) (54c8d07)
• Retry 404 errors in Client.query(...) (#2135) (c6d5f8a)

Dependencies

• Updates required checks list in github (#2136) (fea49ff)
• Use pandas-gbq to determine schema in load_table_from_dataframe (#2095) (7603bd7)

Documentation

• Update magics.rst (#2125) (b5bcfb3)

Changelog

Sourced from google-cloud-bigquery's changelog.

3.31.0 (2025-03-20)

Features

• Add query text and total bytes processed to RowIterator (#2140) (2d5f932)
• Add support for Python 3.13 (0842aa1)

Bug Fixes

• Adding property setter for table constraints, #1990 (#2092) (f8572dd)
• Allow protobuf 6.x (0842aa1)
• Avoid "Unable to determine type" warning with JSON columns in to_dataframe (#1876) (968020d)
• Remove setup.cfg configuration for creating universal wheels (#2146) (d7f7685)

Dependencies

• Remove Python 3.7 and 3.8 as supported runtimes (#2133) (fb7de39)

3.30.0 (2025-02-26)

Features

• Add roundingmode enum, wiring, and tests (#2121) (3a48948)
• Adds foreign_type_info attribute to table class and adds unit tests. (#2126) (2c19681)
• Support resource_tags for table (#2093) (d4070ca)

Bug Fixes

• Avoid blocking in download thread when using BQ Storage API (#2034) (54c8d07)
• Retry 404 errors in Client.query(...) (#2135) (c6d5f8a)

Dependencies

• Updates required checks list in github (#2136) (fea49ff)
• Use pandas-gbq to determine schema in load_table_from_dataframe (#2095) (7603bd7)

Documentation

• Update magics.rst (#2125) (b5bcfb3)

Commits

• 85de1a3 chore(main): release 3.31.0 (#2139)
• 968020d fix: avoid "Unable to determine type" warning with JSON columns in `to_datafr...
• 9acd9c1 chore: refactor cell data parsing to use classes for easier overrides (#2144)
• 0842aa1 fix: Allow protobuf 6.x (#2142)
• d7f7685 fix: remove setup.cfg configuration for creating universal wheels (#2146)
• faeb51d chore: remove unused files (#2141)
• 2d5f932 feat: add query text and total bytes processed to RowIterator (#2140)
• f8572dd fix: adding property setter for table constraints, #1990 (#2092)
• fb7de39 deps: Remove Python 3.7 and 3.8 as supported runtimes (#2133)
• 3a1e3f3 chore(main): release 3.30.0 (#2119)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Update google-cloud-bigquery library to version 3.31.0

New Features:

• Add query text and total bytes processed to RowIterator
• Add support for Python 3.13

Bug Fixes:

• Add property setter for table constraints
• Allow protobuf 6.x
• Avoid 'Unable to determine type' warning with JSON columns in to_dataframe
• Remove setup.cfg configuration for creating universal wheels

[cloudflare-workers-and-pages]

Deploying pyzn with    Cloudflare Pages

Latest commit:	39cb6e7
Status:	✅  Deploy successful!
Preview URL:	https://74bd2d31.pyzn.pages.dev
Branch Preview URL:	https://dependabot-pip-google-cloud-mw28.pyzn.pages.dev

View logs

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the google-cloud-bigquery library from version 3.29.0 to 3.31.0. This includes feature additions such as query text and total bytes processed to RowIterator, support for Python 3.13, rounding mode enum, foreign type info attribute, and resource tags for tables. It also includes bug fixes such as avoiding blocking in the download thread when using the BQ Storage API, retrying 404 errors in Client.query(...), and avoiding 'Unable to determine type' warnings with JSON columns in to_dataframe. Additionally, Python 3.7 and 3.8 are no longer supported.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
The google-cloud-bigquery library has been updated from version 3.29.0 to 3.31.0.	Updated the google-cloud-bigquery dependency version.	Pipfile.lock
Added query text and total bytes processed to RowIterator.	Exposed query text in RowIterator. Exposed total bytes processed in RowIterator.
Added support for Python 3.13.	The library now supports Python 3.13 runtime.
Fixed an issue where JSON columns in to_dataframe would cause an 'Unable to determine type' warning.	Resolved the 'Unable to determine type' warning for JSON columns in to_dataframe.
Removed Python 3.7 and 3.8 as supported runtimes.	The library no longer supports Python 3.7. The library no longer supports Python 3.8.
Added roundingmode enum, wiring, and tests.	Introduced roundingmode enum. Added wiring for roundingmode. Added tests for roundingmode.
Added foreign_type_info attribute to table class and added unit tests.	Added foreign_type_info attribute to table class. Added unit tests for foreign_type_info.
Added support for resource_tags for tables.	Tables now support resource_tags.
Fixed an issue where the download thread would block when using the BQ Storage API.	Resolved blocking issue in download thread when using BQ Storage API.
Client.query(...) now retries 404 errors.	Client.query(...) now retries 404 errors.
Switched to using pandas-gbq to determine schema in load_table_from_dataframe.	load_table_from_dataframe now uses pandas-gbq to determine schema.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[qodo-code-review]

CI Feedback 🧐

(Feedback updated until commit 39cb6e7)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Tests

Failed stage: Start environment [❌]

Failure summary: The action failed because the docker-compose command was not found in the system. The error occurred when trying to execute the command PYZN_VERSION=sha-9641f940ac3fdc2107cf7e732db73cc4eaf8455e docker-compose -f infrastructure/docker-compose.yml --project-directory . up -d on line 446, which resulted in the error /bin/sh: 1: docker-compose: not found and a subsequent make error make: *** [Makefile:6: start-containers] Error 127.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 433: with: 434: registry: ghcr.io 435: username: dependabot[bot] 436: password: *** 437: ecr: auto 438: logout: true 439: ##[endgroup] 440: Logging into ghcr.io... 441: Login Succeeded! 442: ##[group]Run DOCKER_TAG=sha-$GITHUB_SHA make start-containers 443: �[36;1mDOCKER_TAG=sha-$GITHUB_SHA make start-containers�[0m 444: shell: /usr/bin/bash -e {0} 445: ##[endgroup] 446: PYZN_VERSION=sha-9641f940ac3fdc2107cf7e732db73cc4eaf8455e docker-compose -f infrastructure/docker-compose.yml --project-directory . up -d 447: /bin/sh: 1: docker-compose: not found 448: make: *** [Makefile:6: start-containers] Error 127 449: ##[error]Process completed with exit code 2. 450: Post job cleanup.

[codiumai-pr-agent-free]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: dependabot

Failed stage: Approve a PR [❌]

Failure summary: The action failed because GitHub Actions is not permitted to approve pull requests. The error occurred when trying to run the command gh pr review --approve "$PR_URL" (line 50). The specific GraphQL error message was: "GitHub Actions is not permitted to approve pull requests. (addPullRequestReview)".

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 41: outputs.new-version: 3.31.0 42: outputs.compatibility-score: 0 43: outputs.maintainer-changes: false 44: outputs.dependency-group: 45: outputs.alert-state: 46: outputs.ghsa-id: 47: outputs.cvss: 0 48: ##[endgroup] 49: ##[group]Run gh pr review --approve "$PR_URL" 50: �[36;1mgh pr review --approve "$PR_URL"�[0m 51: shell: /usr/bin/bash -e {0} 52: env: 53: PR_URL: https://github.com/khulnasoft/pyzn/pull/32 54: GITHUB_TOKEN: *** 55: ##[endgroup] 56: failed to create review: GraphQL: GitHub Actions is not permitted to approve pull requests. (addPullRequestReview) 57: ##[error]Process completed with exit code 1. 58: Cleaning up orphan processes