Bump the dependabot group with 4 updates

[dependabot]

Bumps the dependabot group with 4 updates: grpcio, h5py, pytest and zipp.

Updates grpcio from 1.71.0 to 1.72.1

Release notes

Sourced from grpcio's releases.

Release v1.72.1

This is release gRPC Core 1.72.1 (gusto).

For gRPC documentation, see grpc.io. For previous releases, see Releases.

This release contains refinements, improvements, and bug fixes, with highlights listed below.

Python

• Pin Cython to 3.1.1 #39609
  • This solves several issues:
    1. #39588: Selecting unstable Cython releases when building gRPC Python artifacts.
    2. Using inconsistent Cython version in released platform-specific wheels within the same grpcio release.
    3. cython/cython#6878 Several published grpcio wheels were built with Cython 3.1.0 and are affected by Cython memory leak issue when using AsyncIO APIs (grpc.aio.*).
• Fix Python 3.12 MacOS universal release artifact #39418

Release v1.72.0

This is release gRPC Core 1.72.0 (gusto).

For gRPC documentation, see grpc.io. For previous releases, see Releases.

This release contains refinements, improvements, and bug fixes.

Release v1.72.0-pre1

This is a prerelease of gRPC Core 1.72.0 (gusto).

For gRPC documentation, see grpc.io. For previous releases, see Releases.

This prerelease contains refinements, improvements, and bug fixes.

Release v1.71.1

This is release gRPC Core 1.71.1 (gears).

For gRPC documentation, see grpc.io. For previous releases, see Releases.

• [RLS] fix use-after-free from accessing config after LB policy shutdown (grpc/grpc#39303)
• [EventEngine] Fix busy loop in thread pool when shutting down (grpc/grpc#39258)

Commits

• 1ca7b98 [Release] Bump version to 1.72.1 (on v1.72.x branch) (#39719)
• 54bd142 [Backport][v1.72]Added #defined to force disable secure_getenv (#39343) (#39715)
• 8a3e247 [SSA] backport fix to 1.72.x (#39704)
• 967170c Fix Python linux distribtest for aarch64_alpine target and enable for presubm...
• e1e0264 [Backport][v1.72.x][Python] Fix Python Linux distribtests copy conflicts (#39...
• 2abb6f3 [Backport][v1.72.x][Python] Pin Cython to 3.1.1 (#39609) (#39632)
• fbd68c7 [Backport][v1.72.x] Fix Python 3.12 MacOS release artifact (#39418) (#39504)
• 84c340d [Backport][v1.72.x] Protect grpc generated sources from unwanted system macro...
• 3b179f8 [Backport-v1.72.x] [Build] Fix use_openssl=true (#39420)
• 6c47208 [RLS] fix use-after-free from accessing config after LB policy shutdown (v1.7...
• Additional commits viewable in compare view

Updates h5py from 3.13.0 to 3.14.0

Changelog

Sourced from h5py's changelog.

.. _release_guide:

Release Guide

Steps to make an h5py release:

1. Have a look for any open issues or PRs which we might want to solve/merge before the release.

2. Prepare a new branch, e.g. git switch -c prepare-3.14

3. Prepare the release notes. The goal is to describe changes visible to users & repackagers of h5py in a form that doesn't assume 'internal' development knowledge. If something breaks, or behaviour changes unexpectedly, the release notes should let someone make a good guess which change is involved.

   • Check for recent merged PRs with no milestone <https://github.com/h5py/h5py/pulls?q=is%3Amerged+is%3Apr+no%3Amilestone>_, and assign them to the current release milestone. We can ignore PRs which only touch CI with no consequences for users.
   • Go to the milestone page. If there are open issues/PRs there, decide whether to include or defer them.
   • Assemble the release notes in docs/whatsnew based on the list of merged PRs. Commit the changes.

4. Update the version number & commit the changes. The files that need changing are:

   • setup.py
   • h5py/version.py
   • docs/conf.py

5. Push the branch, open a PR, wait for the CI. Check the RTD build for the newly added release notes (formatting & cross-links). Optionally, wait for other maintainers to check it as well.

6. When everything looks good, merge the PR.

7. Checkout the master branch, pull, make and push the tag, which will cause CI to build wheels & make a GitHub release::

   git switch master git pull git tag 3.14.0 # <-- change this git push --tags

8. Prepare the sdist::

   git clean -xfdi python -m build --sdist

9. Download the wheels: gh release download 3.14.0 -D dist/

10. Upload to PyPI: twine upload dist/h5py-3.14.0* - this requires a token from PyPI, which must be supplied to twine <https://twine.readthedocs.io/en/stable/#configuration>_.

... (truncated)

Commits

• 07a5511 Merge pull request #2591 from takluyver/prepare-3.14
• a70e013 Add versionadded box for numpy strings support
• 6186edf Version number -> 3.14.0
• a9e2d46 Add release notes for 3.14
• ab19424 Merge pull request #2585 from ArvidJB/fork_thread_phil
• 60c5cd9 Merge pull request #2590 from neutrinoceros/tst/bump-windows-image
• e3cc528 MNT: bump windows image on azure (2019 -> 2022)
• a51de9f Time out tests on deadlock instead of hanging and leaving zombie processes be...
• 7c14cd9 Merge pull request #2586 from takluyver/h5d-write-chunk
• a92ab7c Address review comments
• Additional commits viewable in compare view

Updates pytest from 8.3.5 to 8.4.0

Release notes

Sourced from pytest's releases.

8.4.0

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.

... (truncated)

Commits

• 315b3ae Prepare release version 8.4.0
• 1498ba3 Merge pull request #13467 from pytest-dev/towncrier-create
• e4389ac Remove resultlog from the docs (#13465)
• 64b2301 scripts/release: add missing build to towncrier call
• 4c205cf testing/plugins_integration: update Django (#13463)
• 4dcbcc9 Merge pull request #13458 from pytest-dev/dup-param-error
• 5293016 Merge pull request #13459 from pytest-dev/pyright-minor-fixes
• 7a48181 Add pyright configuration
• 9fc6db9 pytester: avoid confusing x self parameter
• 9aa198b mark/expression: fix self -> cls
• Additional commits viewable in compare view

Updates zipp from 3.22.0 to 3.23.0

Changelog

Sourced from zipp's changelog.

v3.23.0

Features

• Add a compatibility shim for Python 3.13 and earlier. (#145)

Commits

• ccb4111 Finalize
• 5b5725d Merge pull request #146 from jaraco/debt/backport-gh-133337
• c1dca82 Remove unused dependency.
• 717d770 Add a compatibility shim for Python 3.13 and earlier.
• d860de4 gh-133306: Use \z instead of \Z in regular expressions in the stdlib (GH-133337)
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[coveralls]

Pull Request Test Coverage Report for Build 15529244122

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 87.111%

---

Totals
Change from base Build 15527218631:	0.0%
Covered Lines:	2433
Relevant Lines:	2793

---

💛 - Coveralls