v2.41.1

Compare Source

Bug Fixes

• Suppress deprecation warning for ADC (#​1815) (751ce3f)

v2.41.0

Compare Source

Features

• Add support for cachetools 6.0 (#​1773) (af18060)
• Add trust boundary support for service accounts and impersonation. (#​1778) (99be2ce)

Bug Fixes

• Deprecating load_credentials_from_dict (58b66ec)
• Deprecating load_credentials_from_file (58b66ec)
• Fix type error in credentials.py for python 3.7 and 3.8 (#​1805) (c30a6a7)

Documentation

• Update user guide to include x509 feature. (#​1802) (2d89ab4)

v2.40.3

Compare Source

Bug Fixes

• Auth fetch token from default endpoint (#​1779) (88891cc)
• Remove unnecessary call to mds service (#​1769) (7c61c7d)
• Retry 504 errors (#​1767) (554f967)

v2.40.2

Compare Source

Bug Fixes

• Remove sync response logs in AuthorizedSession (97ed1c8)
• Update test to consider new error message from cryptography (#​1765) (44e38b6)

v2.40.1

Compare Source

Bug Fixes

• Disable logging response body for async logs (#​1756) (2f0ddfe)

v2.40.0

Compare Source

Features

• Add request response logging to auth (#​1678) (77ad53e)

Bug Fixes

• Correct webauthn JSON parsing to be compliant with standard. (#​1658) (0c5ef36)

v2.39.0

Compare Source

Features

• Adds GA support for X.509 workload identity federation (#​1695) (7495960)

Bug Fixes

• Add impersonated SA via local ADC support for fetch_id_token (#​1740) (f249764)
• Add missing packaging dependency for feature requiring urllib3 (#​1732) (221f4a8)
• Add request timeout for MDS requests (#​1699) (9f7d3fa)
• Explicitly declare support for Python 3.13 (#​1741) (6fd04d5)

v1.40.0: google-cloud-compute 1.40.0

Compare Source

Features

• Update Compute Engine v1 API to revision 2025091 (#​1107) (4dc7381c)

v1.39.0: google-cloud-compute 1.39.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025090 (4e5a0b5)

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025090 (4e5a0b5)

v1.38.0: google-cloud-compute: v1.38.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025090 (#​14434) (daf5ab8)

v1.37.0: google-cloud-compute: v1.37.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025081 (#​1091) (#​14324) (6cdbcee)

v1.36.0: google-cloud-compute: v1.36.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025080 (51732d3)

v1.35.0: google-cloud-compute: v1.35.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025072 (#​1081) (#​14196) (9abaf2f)
• [google-cloud-compute] Update Compute Engine v1 API to revision 2025072 (#​1085) (#​14199) (17c935f)

v1.34.0: google-cloud-compute: v1.34.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025071 (#​1074) (#​14169) (0c26f13)

v1.33.0: google-cloud-compute: v1.33.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025070 (#​1073) (#​14107) (723ac5d)

v1.32.0: google-cloud-compute: v1.32.0

Compare Source

Features

• Update Compute Engine v1 API to revision 2025062 (3ad8819)

v1.31.0: google-cloud-compute: v1.31.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine v1 API to revision 2025060 (#​13970) (8083640)
• Update Compute Engine v1 API to revision 2025051 (#​1047) (8083640)

v1.30.0: google-cloud-compute: v1.30.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine API to revision 2025041 (#​13800) (ae6a7c9)

v1.29.0: google-cloud-compute: v1.29.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine API to revision 2025032 (#​13710) (da0e811)

v1.28.0: google-cloud-compute: v1.28.0

Compare Source

Features

• [google-cloud-compute] Update Compute Engine API to revision (9be352b)
• Update Compute Engine API to revision 2025030 (#​13678) (9be352b)

v1.27.0

Compare Source

v1.26.0

Compare Source

v1.25.0

Compare Source

v1.24.0

Compare Source

v1.23.0

Compare Source

v1.22.0

Compare Source

v1.21.0

Compare Source

v1.20.1

Compare Source

v1.20.0

Compare Source

v1.19.2

Compare Source

v1.19.1

Compare Source

v1.19.0: google-cloud-bigquery-connection 1.19.0

Compare Source

1.19.0 (2025-10-16)

v1.18.0: google-cloud-workflows: v1.18.0

Compare Source

Features

• add crypto key config to Workflow (036658f)
• add ExecutionHistoryLevel enum (036658f)
• add ExecutionHistoryLevel to Workflow (036658f)
• add ListWorkflowRevisions method (036658f)
• add tags to Workflow (036658f)

Documentation

• update Workflow some standard field docs (036658f)

v1.17.0

Compare Source

v1.16.1

Compare Source

v1.16.0

Compare Source

v1.15.0

Compare Source

v1.14.1

v1.14.0

v1.13.0

v1.12.1

v1.12.0

v1.11.0

v1.6.1

v1.6.0

v3.4.1

Compare Source

Bug Fixes

• Fixes #​1561 by adding an option to specify the entire object checksum for resumable uploads via the upload_from_string, upload_from_file, and upload_from_filename methods (acb918e)

v3.4.0

Compare Source

Features

• experimental: Add async grpc client (#​1537) (ac57b8d)
• experimental: Add grpc client (#​1533) (5674587)

Bug Fixes

• GAPIC generation failed with 'Directory not empty' (#​1542) (c80d820)

v3.3.1

Compare Source

Bug Fixes

• Provide option to user to set entire object checksum at "initiate a resumable upload session" and send the same (#​1525) (a8109e0)
• Send part's checksum for XML MPU part upload (#​1529) (2ad77c7)

v3.3.0

Compare Source

Features

• Add support for bucket IP filter (#​1516) (a29073c)

Bug Fixes

• Add logs on AssertionError for issue #​1512 (#​1518) (6a9923e)

Documentation

• Update the documentation of move_blob function (#​1507) (72252e9)

v3.2.0

Compare Source

Features

• Adding support of single shot download (#​1493) (61c5d5f)

v3.1.1

Compare Source

Bug Fixes

• Add a check for partial response data (#​1487) (7e0412a)
• Add trove classifier for Python 3.13 (0100916)
• deps: Require google-crc32c >= 1.1.3 (0100916)
• deps: Require protobuf >= 3.20.2, < 7.0.0 (0100916)
• deps: Require requests >= 2.22.0 (0100916)
• Remove setup.cfg configuration for creating universal wheels (#​1448) (d3b6b3f)
• Resolve issue where pre-release versions of dependencies are installed (0100916)
• Segmentation fault in tink while writing data (#​1490) (2a46c0b)

Documentation

• Move quickstart to top of readme (#​1451) (53257cf)
• Update README to break infinite redirect loop (#​1450) (03f1594)

v8.4.2

Compare Source

pytest 8.4.2 (2025-09-03)

Bug fixes

• #​13478: Fixed a crash when using console_output_style{.interpreted-text role="confval"} with times and a module is skipped.

• #​13530: Fixed a crash when using pytest.approx{.interpreted-text role="func"} and decimal.Decimal{.interpreted-text role="class"} instances with the decimal.FloatOperation{.interpreted-text role="class"} trap set.

• #​13549: No longer evaluate type annotations in Python 3.14 when inspecting function signatures.

  This prevents crashes during module collection when modules do not explicitly use from __future__ import annotations and import types for annotations within a if TYPE_CHECKING: block.

• #​13559: Added missing [int]{.title-ref} and [float]{.title-ref} variants to the [Literal]{.title-ref} type annotation of the [type]{.title-ref} parameter in pytest.Parser.addini{.interpreted-text role="meth"}.

• #​13563: pytest.approx{.interpreted-text role="func"} now only imports numpy if NumPy is already in sys.modules. This fixes unconditional import behavior introduced in [8.4.0]{.title-ref}.

Improved documentation

• #​13577: Clarify that pytest_generate_tests is discovered in test modules/classes; other hooks must be in conftest.py or plugins.

Contributor-facing changes

• #​13480: Self-testing: fixed a few test failures when run with -Wdefault or a similar override.
• #​13547: Self-testing: corrected expected message for test_doctest_unexpected_exception in Python 3.14.
• #​13684: Make pytest's own testsuite insensitive to the presence of the CI environment variable -- by ogrisel{.interpreted-text role="user"}.

v8.4.1

Compare Source

pytest 8.4.1 (2025-06-17)

Bug fixes

• #​13461: Corrected _pytest.terminal.TerminalReporter.isatty to support
  being called as a method. Before it was just a boolean which could
  break correct code when using -o log_cli=true).

• #​13477: Reintroduced pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.

  This warning is raised when a test functions returns a value other than None, which is often a mistake made by beginners.

  See return-not-none{.interpreted-text role="ref"} for more information.

• #​13497: Fixed compatibility with Twisted 25+.

Improved documentation

• #​13492: Fixed outdated warning about faulthandler not working on Windows.

v8.4.0

Compare Source

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

• #​11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.

• #​12346: Tests will now fail, instead of raising a warning, if they return any value other than None.

• #​12874: We dropped support for Python 3.8 following its end of life (2024-10-07).

• #​12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

  See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

• #​10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.

New features

• #​11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.

• #​12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.

• #​12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.

• #​12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

  This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.

• #​12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

  For example:

contents of src/domain.py

class Testament: ...

contents of tests/test_testament.py

from domain import Testament

def test_testament(): ...
```

In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.

This behavior can now be prevented by setting the new `collect_imported_tests`{.interpreted-text role="confval"} configuration option to `false`, which will make pytest collect classes/functions from test files **only** if they are defined in that file.

\-- by `FreerGit`{.interpreted-text role="user"}

• #​12765: Thresholds to trigger snippet truncation can now be set with truncation_limit_lines{.interpreted-text role="confval"} and truncation_limit_chars{.interpreted-text role="confval"}.

  See truncation-params{.interpreted-text role="ref"} for more information.

• #​13125: console_output_style{.interpreted-text role="confval"} now supports times to show execution time of each test.

• #​13192: pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string to match, as this will match against any value. Use match="^$" if you want to check that an exception has no message.

• #​13192: pytest.raises{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has ^ and $ and is otherwise escaped.

• #​13192: You can now pass with pytest.raises(check=fn): <pytest.raises>{.interpreted-text role="func"}, where fn is a function which takes a raised exception and returns a boolean. The raises fails if no exception was raised (as usual), passes if an exception is raised and fn returns True (as well as match and the type matching, if specified, which are checked before), and propagates the exception if fn returns False (which likely also fails the test).

• #​13228: hidden-param{.interpreted-text role="ref"} can now be used in id of pytest.param{.interpreted-text role="func"} or in
  ids of Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"}.
  It hides the parameter set from the test name.

• #​13253: New flag: --disable-plugin-autoload <disable_plugin_autoload>{.interpreted-text role="ref"} which works as an alternative to PYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files with addopts{.interpreted-text role="confval"}.

Improvements in existing functionality

• #​10224: pytest's short and long traceback styles (how-to-modifying-python-tb-printing{.interpreted-text role="ref"})
  now have partial 657{.interpreted-text role="pep"} support and will show specific code segments in the
  traceback.

  ================================= FAILURES =================================
  _______________________ test_gets_correct_tracebacks _______________________
  
  test_tracebacks.py:12: in test_gets_correct_tracebacks
      assert manhattan_distance(p1, p2) == 1
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  test_tracebacks.py:6: in manhattan_distance
      return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)
                             ^^^^^^^^^
  E   AttributeError: 'NoneType' object has no attribute 'x'
  

  -- by ammaraskar{.interpreted-text role="user"}

• #​11118: Now pythonpath{.interpreted-text role="confval"} configures [$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the [-p]{.title-ref} command-line option.

  -- by millerdev{.interpreted-text role="user"}

• #​11381: The type parameter of the parser.addini method now accepts ["int"]{.title-ref} and "float" parameters, facilitating the parsing of configuration values in the configuration file.

  Example:

  def pytest_addoption(parser):
      parser.addini("int_value", type="int", default=2, help="my int value")
      parser.addini("float_value", type="float", default=4.2, help="my float value")

  The [pytest.ini]{.title-ref} file:

  [pytest]
  int_value = 3
  float_value = 5.4

• #​11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.

  -- by the-compiler{.interpreted-text role="user"} and glyphack{.interpreted-text role="user"}

• #​12426: A warning is now issued when pytest.mark.usefixtures ref{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.

• #​12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.

• #​12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.

  This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.

• #​12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.

• #​12958: A number of unraisable <unraisable>{.interpreted-text role="ref"} enhancements:

  • Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions.
  • Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions.
  • Collect multiple unraisable exceptions per test phase.
  • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
  • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
  • Report the unraisable exception as the cause of the pytest.PytestUnraisableExceptionWarning{.interpreted-text role="class"} exception if raised.
  • Compute the repr of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.

• #​13010: pytest.approx{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.

• #​13016: A number of threadexception <unraisable>{.interpreted-text role="ref"} enhancements:

  • Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads.
  • Collect multiple thread exceptions per test phase.
  • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
  • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
  • Report the thread exception as the cause of the pytest.PytestUnhandledThreadExceptionWarning{.interpreted-text role="class"} exception if raised.
  • Extract the name of the thread object in the excepthook which should help with resurrection of the thread.

• #​13031: An empty parameter set as in pytest.mark.parametrize([], ids=idfunc) will no longer trigger a call to idfunc with internal objects.

• #​13115: Allows supplying ExceptionGroup[Exception] and BaseExceptionGroup[BaseException] to pytest.raises to keep full typing on ExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"}:

  with pytest.raises(ExceptionGroup[Exception]) as exc_info:
      some_function()

  Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.

• #​13122: The --stepwise mode received a number of improvements:

  • It no longer forgets the last failed test in case pytest is executed later without the flag.

    This enables the following workflow:

    1. Execute pytest with --stepwise, pytest then stops at the first failing test;
    2. Iteratively update the code and run the test in isolation, without the --stepwise flag (for example in an IDE), until it is fixed.
    3. Execute pytest with --stepwise again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.

    Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.

    This change however might cause issues if the --stepwise mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).

  • New --stepwise-reset/--sw-reset flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.

• #​13308: Added official support for Python 3.14.

• #​13380: Fix ExceptionGroup{.interpreted-text role="class"} traceback filtering to exclude pytest internals.

• #​13415: The author metadata of the BibTex example is now correctly formatted with last names following first names.
  An example of BibLaTex has been added.
  BibTex and BibLaTex examples now clearly indicate that what is cited is software.

  -- by willynilly{.interpreted-text role="user"}

• #​13420: Improved test collection performance by optimizing path resolution used in FSCollector.

• #​13457: The error message about duplicate parametrization no longer displays an internal stack trace.

• #​4112: Using pytest.mark.usefixtures <pytest.mark.usefixtures ref>{.interpreted-text role="ref"} on pytest.param{.interpreted-text role="func"} now produces an error instead of silently doing nothing.

• #​5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling pytest.main{.interpreted-text role="func"}.

[#​6985](https://redirect.github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.

:   -   The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.

    -   Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 ± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 ± 1]{.title-ref}).

        Example:

        **Previous Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1.0e+00
        ```

        **Current Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1
        ```

    \-- by `fazeelghafoor`{.interpreted-text role="user"}

• #​7683: The formerly optional pygments dependency is now required, causing output always to be source-highlighted (unless disabled via the --code-highlight=no CLI option).

Bug fixes

• #​10404: Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible
  so that wa