This PR contains the following updates:

Package	Change	Age	Confidence
google-cloud-bigquery	==3.38.0 → ==3.40.1
google-cloud-bigquery-storage (source)	==2.33.1 → ==2.36.2
google-cloud-testutils	==1.6.4 → ==1.7.0
pandas	==2.3.3 → ==3.0.1
pandas-gbq	==0.29.2 → ==0.33.0
pyarrow	==22.0.0 → ==23.0.1
pyarrow	==21.0.0 → ==23.0.1
pytest (changelog)	==8.4.2 → ==9.0.2

Release Notes

v3.40.1

Compare Source

Documentation

• clarify that only jobs.query and jobs.getQueryResults are affec… (#​2349) (73228432a3c821db05d898ea4a4788adf15b033d)

Bug Fixes

• updates timeout/retry code to respect hanging server (#​2408) (24d45d0d5bf89762f253ba6bd6fdbee9d5993422)
• add timeout parameter to to_dataframe and to_arrow met… (#​2354) (4f67ba20b49159e81f645ed98e401b9bb1359c1a)

v3.40.0

Compare Source

Features

• support load_table and list_rows with picosecond timestamp (#​2351) (46764a59ca7a21ed14ad2c91eb7f98c302736c22)
• support timestamp_precision in table schema (#​2333) (8d5785aea50b9f9e5b13bd4c91e8a08d6dac7778)

v3.39.0

Compare Source

Documentation

• remove experimental annotations from GA features (#​2303) (1f1f9d41e8a2c9016198d848ad3f1cbb88cf77b0)

Features

• adds support for Python runtime 3.14 (#​2322) (6065e14c448cb430189982dd70025fa0575777ca)
• Add ExternalRuntimeOptions to BigQuery routine (#​2311) (fa76e310a16ea6cba0071ff1d767ca1c71514da7)

Bug Fixes

• include io.Base in the PathType (#​2323) (b11e09cb6ee32e451b37eda66bece2220b9ceaba)
• honor custom retry in job.result() (#​2302) (e118b029bbc89a5adbab83f39858c356c23665bf)
• remove ambiguous error codes from query retries (#​2308) (8bbd3d01026c493dfa5903b397d2b01c0e9bf43b)

v2.36.2: google-cloud-bigquery-storage: v2.36.2

Compare Source

Bug Fixes

• missing first page in to_dataframe (#​15575) (397fb147)

v2.36.1: google-cloud-bigquery-storage: v2.36.1

Compare Source

Bug Fixes

• fix mypy (#​15531) (f2536ae3)

Documentation

• Update BigQuery Storage Arrow samples batching logic (#​14961) (45d4cee9)

v2.36.0: google-cloud-speech 2.36.0

Compare Source

Features

• update min_speaker_count and max_speaker_count to be optional (PiperOrigin-RevId: 8523832) (b3cb4de3)

• add custom prompt config in the request and return prompt in the response (PiperOrigin-RevId: 8523832) (b3cb4de3)

Documentation

• Clarify that min_speaker_count and max_speaker_count in SpeakerDiarizationConfig are not currently used (PiperOrigin-RevId: 8523832) (b3cb4de3)

• Update guidance on how to enable speaker diarization; to enable, set the diarization_config field to an empty SpeakerDiarizationConfig message (PiperOrigin-RevId: 8523832) (b3cb4de3)

v2.35.0: google-cloud-bigquery-storage 2.35.0

Compare Source

Features

• Support picosecond timestamp precision in BigQuery Storage API (PiperOrigin-RevId: 8294868) (5093802d)

v2.34.0: google-cloud-bigquery-storage 2.34.0

Compare Source

Features

• Add support for Python 3.14 (bd0f5422)

Bug Fixes

• Deprecate credentials_file argument (bd0f5422)

• Require grpcio >= 1.33.2 (bd0f5422)

• Require grpcio >= 1.75.1 for Python 3.14 (bd0f5422)

v1.7.0

Compare Source

Features

• Add Python 3.14 support (#​284) (3cb8491)

v3.0.1: pandas 3.0.1

Compare Source

We are pleased to announce the release of pandas 3.0.1.
This is a patch release in the 3.0.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.0.x series upgrade to this version.

See the full whatsnew for a list of all the changes.

Pandas 3.0.0 supports Python 3.11 and higher.
The release can be installed from PyPI:

python -m pip install --upgrade pandas==3.0.*

Or from conda-forge

conda install -c conda-forge pandas=3.0

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

v3.0.0: pandas 3.0.0

Compare Source

We are pleased to announce the release of pandas 3.0.0, a major release from the pandas 2.x series. This release includes some new features, bug fixes, and performance improvements, as well as possible breaking changes.

The pandas 3.0 release removed a functionality that was deprecated in previous releases. It is recommended to first upgrade to pandas 2.3 and to ensure your code is working without warnings, before upgrading to pandas 3.0.

Highlights include:

• Dedicated string data type by default
• Consistent copy/view behaviour with Copy-on-Write (CoW) (a.k.a. getting rid of the SettingWithCopyWarning)
• New default resolution for datetime-like data
• Initial support for the new pd.col syntax

See the full whatsnew for a list of all the changes.

Pandas 3.0.0 supports Python 3.11 and higher.
The release can be installed from PyPI

python -m pip install --upgrade pandas==3.0.*

Or from conda-forge

conda install -c conda-forge pandas=3.0

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

v0.33.0

Compare Source

Features

• add dry run to the read_gbq function (#​979) (516f986f6935c9a6426e6a9b1702cb2002916362)

v0.32.0

Compare Source

Features

• Add support for Python 3.14 (#​976) (89b008d81e5992966ccab675511bc944682d0549)

Bug Fixes

• boolean round-trip test and CSV datetime loading errors (#​1000) (d4431030e1b537e12f850d8206741b62ff4d7d67)

v0.31.1

Compare Source

Dependencies

• Temporarily mark as incompatible with pandas 3.0

v0.31.0

Compare Source

Features

• add pandas_gbq.sample (#​983) (ac771c12f58b7378a8550515c9c656da7fa980a8)

v0.30.0

Compare Source

Features

• Add partitioning and clustering parameters to the to_gbq function (#​949) (e7213c7)
• Allow loading a DataFrame even if the provided BigQuery schema includes columns not in the DataFrame (#​953) (a529505)

v9.0.2

Compare Source

pytest 9.0.2 (2025-12-06)

Bug fixes

• #​13896: The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.

  You may enable it again by passing -p terminalprogress. We may enable it by default again once compatibility improves in the future.

  Additionally, when the environment variable TERM is dumb, the escape codes are no longer emitted, even if the plugin is enabled.

• #​13904: Fixed the TOML type of the tmp_path_retention_count settings in the API reference from number to string.

• #​13946: The private config.inicfg attribute was changed in a breaking manner in pytest 9.0.0.
  Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
  It will be deprecated in pytest 9.1 and removed in pytest 10.

• #​13965: Fixed quadratic-time behavior when handling unittest subtests in Python 3.10.

Improved documentation

• #​4492: The API Reference now contains cross-reference-able documentation of pytest's command-line flags <command-line-flags>.

v9.0.1

Compare Source

pytest 9.0.1 (2025-11-12)

Bug fixes

• #​13895: Restore support for skipping tests via raise unittest.SkipTest.
• #​13896: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
• #​13904: Fixed the TOML type of the verbosity settings in the API reference from number to string.
• #​13910: Fixed UserWarning: Do not expect file_or_dir on some earlier Python 3.12 and 3.13 point versions.

Packaging updates and notes for downstreams

• #​13933: The tox configuration has been adjusted to make sure the desired
  version string can be passed into its package_env through
  the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
  variable as a part of the release process -- by webknjaz.

Contributor-facing changes

• #​13891, #​13942: The CI/CD part of the release automation is now capable of
  creating GitHub Releases without having a Git checkout on
  disk -- by bluetech and webknjaz.
• #​13933: The tox configuration has been adjusted to make sure the desired
  version string can be passed into its package_env through
  the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
  variable as a part of the release process -- by webknjaz.

v9.0.0

Compare Source

pytest 9.0.0 (2025-11-05)

New features

• #​1367: Support for subtests has been added.

  subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

  Example:

  def contains_docstring(p: Path) -> bool:
      """Return True if the given Python file contains a top-level docstring."""
      ...
  
  def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
      for path in Path.cwd().glob("*.py"):
          with subtests.test(path=str(path)):
              assert contains_docstring(path)

  Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

  In addition, unittest.TestCase.subTest is now also supported.

  This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.

  [!NOTE]
  This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

• #​13743: Added support for native TOML configuration files.

  While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options],
  it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
  Now, pytest supports the native TOML data model.

  In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.

  # pyproject.toml
  [tool.pytest]
  minversion = "9.0"
  addopts = ["-ra", "-q"]
  testpaths = [
      "tests",
      "integration",
  ]

  The [tool.pytest.ini_options] table remains supported, but both tables cannot be used at the same time.

  If you prefer to use a separate configuration file, or don't use pyproject.toml, you can use pytest.toml or .pytest.toml:

  # pytest.toml or .pytest.toml
  [pytest]
  minversion = "9.0"
  addopts = ["-ra", "-q"]
  testpaths = [
      "tests",
      "integration",
  ]

  The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

  See config file formats for full details.

• #​13823: Added a "strict mode" enabled by the strict configuration option.

  When set to true, the strict option currently enables

  • strict_config
  • strict_markers
  • strict_parametrization_ids
  • strict_xfail

  The individual strictness options can be explicitly set to override the global strict setting.

  The previously-deprecated --strict command-line flag now enables strict mode.

  If pytest adds new strictness options in the future, they will also be enabled in strict mode.
  Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
  or if you want to proactively adopt new strictness options as they are added.

  See strict mode for more details.

• #​13737: Added the strict_parametrization_ids configuration option.

  When set, pytest emits an error if it detects non-unique parameter set IDs,
  rather than automatically making the IDs unique by adding 0, 1, ... to them.
  This can be particularly useful for catching unintended duplicates.

• #​13072: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence.
  When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
  you'll see the progress in the terminal tab or window,
  allowing you to monitor pytest's progress at a glance.

  This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:

  • On a user level, using -p no:terminalprogress on the command line or via an environment variable PYTEST_ADDOPTS='-p no:terminalprogress'.
  • On a project configuration level, using addopts = "-p no:terminalprogress".

• #​478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.

  Previously, this option only impacted package imports, now it also impacts tests discovery.

• #​13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock.

  Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process.

  -- by ogrisel.

• #​13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.

  Plugins can now register alternative names for configuration options,
  allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
  The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.

Improvements in existing functionality

• #​13330: Having pytest configuration spread over more than one file (for example having both a pytest.ini file and pyproject.toml with a [tool.pytest.ini_options] table) will now print a warning to make it clearer to the user that only one of them is actually used.

  -- by sgaist

• #​13574: The single argument --version no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

  Passing --version twice (e.g., pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.

  [!NOTE]
  Since --version is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as PYTEST_ADDOPTS or addopts.

• #​13823: Added strict_xfail as an alias to the xfail_strict option,
  strict_config as an alias to the --strict-config flag,
  and strict_markers as an alias to the --strict-markers flag.
  This makes all strictness options consistently have configuration options with the prefix strict_.

• #​13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.

• #​13732: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.

• #​13859: Clarify the error message for pytest.raises() when a regex match fails.

• #​13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".

Removals and backward incompatible breaking changes

• #​12083: Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/.

  The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

  1. pytest a/b a/ or pytest a/ a/b are equivalent to pytest a; if an argument overlaps another arguments, only the prefix remains.
  2. pytest x.py x.py is equivalent to pytest x.py; previously such an invocation was taken as an explicit request to run the tests from the file twice.

  If you rely on these behaviors, consider using --keep-duplicates <duplicate-paths>, which retains its existing behavior (including the bug).

• #​13719: Support for Python 3.9 is dropped following its end of life.

• #​13766: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD_NUMBER was defined;
  now, CI mode is only activated if at least one of those variables is defined and set to a non-empty value.

• #​13779: PytestRemovedIn9Warning deprecation warnings are now errors by default.

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type PytestRemovedIn9Warning now generate errors
  instead of warning messages by default.

  The affected features will be effectively removed in pytest 9.1, so please consult the
  deprecations section in the docs for directions on how to update existing code.

  In the pytest 9.0.X series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your pytest.ini file:

  [pytest]
  filterwarnings =
      ignore::pytest.PytestRemovedIn9Warning

  But this will stop working when pytest 9.1 is released.

  If you have concerns about the removal of a specific feature, please add a
  comment to 13779.

Deprecations (removal in next major release)

• #​13807: monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend> now issues a deprecation warning when the prepended path contains legacy namespace packages (those using pkg_resources.declare_namespace()).
  Users should migrate to native namespace packages (420).
  See monkeypatch-fixup-namespace-packages for details.

Bug fixes

• #​13445: Made the type annotations of pytest.skip and friends more spec-complaint to have them work across more type checkers.

• #​13537: Fixed a bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.

• #​13598: Fixed possible collection confusion on Windows when short paths and symlinks are involved.

• #​13716: Fixed a bug where a nonsensical invocation like pytest x.py[a] (a file cannot be parametrized) was silently treated as pytest x.py. This is now a usage error.

• #​13722: Fixed a misleading assertion failure message when using pytest.approx on mappings with differing lengths.

• #​13773: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.

• #​13816: Fixed pytest.approx which now returns a clearer error message when comparing mappings with different keys.

• #​13849: Hidden .pytest.ini files are now picked up as the config file even if empty.
  This was an inconsistency with non-hidden pytest.ini.

• #​13865: Fixed --show-capture with --tb=line.

• #​13522: Fixed pytester in subprocess mode ignored all :attr`pytester.plugins <pytest.Pytester.plugins>` except the first.

  Fixed pytester in subprocess mode silently ignored non-str pytester.plugins <pytest.Pytester.plugins>.
  Now it errors instead.
  If you are affected by this, specify the plugin by name, or switch the affected tests to use pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess> explicitly instead.

Packaging updates and notes for downstreams

• #​13791: Minimum requirements on iniconfig and packaging were bumped to 1.0.1 and 22.0.0, respectively.

Contributor-facing changes

• #​12244: Fixed self-test failures when TERM=dumb.
• #​12474: Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.
• #​13621: pytest's own testsuite now handles the lsof command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds.
• #​13638: Fixed deprecated gh pr new command in scripts/prepare-release-pr.py.
  The script now uses gh pr create which is compatible with GitHub CLI v2.0+.
• #​13695: Flush stdout and stderr in Pytester.run to avoid truncated outputs in test_faulthandler.py::test_timeout on CI -- by ogrisel.
• #​13771: Skip test_do_not_collect_symlink_siblings on Windows environments without symlink support to avoid false negatives.
• #​13841: tox>=4 is now required when contributing to pytest.
• #​13625: Added missing docstrings to pytest_addoption(), pytest_configure(), and cacheshow() functions in cacheprovider.py.

Miscellaneous internal changes

• #​13830: Configuration overrides (-o/--override-ini) are now processed during startup rather than during config.getini() <pytest.Config.getini>.

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• If you want to rebase/retry this PR, check this box

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