Skip to content

chore(deps): update python packages#314

Open
renovate[bot] wants to merge 1 commit intomainfrom
users/renovate/python
Open

chore(deps): update python packages#314
renovate[bot] wants to merge 1 commit intomainfrom
users/renovate/python

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 7, 2026

This PR contains the following updates:

Package Change Age Confidence
bandit (source, changelog) 1.9.31.9.4 age confidence
grpcio 1.78.01.80.0 age confidence
mypy (changelog) 1.19.11.20.0 age confidence
pytest-cov (changelog) 7.0.07.1.0 age confidence
sphinx-autoapi 3.7.03.8.0 age confidence
types-pywin32 (changelog) 311.0.0.20251008311.0.0.20260323 age confidence

Release Notes

PyCQA/bandit (bandit)

v1.9.4

Compare Source

What's Changed
New Contributors

Full Changelog: PyCQA/bandit@1.9.3...1.9.4

grpc/grpc (grpcio)

v1.80.0

Compare Source

This is release 1.80.0 (glimmering) of gRPC Core.

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

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

Core

  • [ssl] Implement TLS private key signer in Python. (#​41701)
  • [TLS Credentials]: Private Key Offload Implementation. (#​41606)
  • Fix max sockaddr struct size on OpenBSD. (#​40454)
  • [core] Enable EventEngine for Python by default, and EventEngine fork support in Python and Ruby. (#​41432)
  • [TLS Credentials]: Create InMemoryCertificateProvider to update certificates independently. (#​41484)
  • [Ruby] Build/test ruby 4.0 and build native gems with Ruby 4.0 support. (#​41324)
  • [EventEngine] Remove an incorrect std::move in DNSServiceResolver constructor. (#​41502)
  • [RR and WRR] enable change to connect from a random index. (#​41472)
  • [xds] Implement gRFC A101. (#​41051)

C++

  • [C++] Add SNI override option to C++ channel credentials options API. (#​41460)

C#

Objective-C

  • [Fix][Compiler] Plugins fall back to the edition 2023 for older protobuf. (#​41357)

PHP

  • [PHP] Disable php infinite recursion check for callback from Core to PHP. (#​41835)
  • [PHP] Fix runtime error with PHp8.5 alpha because zend_exception_get_defaul…. (#​40337)

Python

  • [Python] Fix GRPC_TRACE not working when absl log initialized in cython. (#​41814)
  • Revert "[Python] Align GRPC_ENABLE_FORK_SUPPORT env defaults in core and python (#​41455)". (#​41769)
  • [Python] Fix AsyncIO Server maximum_concurrent_rpcs enforcement preventing negative active_rpcs count. (#​41532)
  • [Python] Docs: correct grpc.Compression references. (#​41705)
  • [Python] [Typeguard] Part 4 - Add Typeguard to AIO stack in tests . (#​40226)
  • [Python] Fix multi-thread exception for Asyncio gRPC clients - Fixes #​25364. (#​41483)
  • [Python] Resolve absl::InitializeLog warning. (#​39779)
  • [Python] Remove IF usage in Cython. (#​41400)
  • [Python] Add language features to exported proto files. (#​41501)
  • [Python] Fix crash when iterating on AIO Metadata keys(), values(), items() or list(metadata.values()) etc. . (#​41481)
  • [Python] Modernize and revamp Public API Docs. (#​41287)

Ruby

  • [Ruby] Added support to push native-debug packages off rubygems to public gcs bucket. (#​41270)

v1.78.1

Compare Source

This is release 1.78.1 (gutsy) of gRPC Core.

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

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

Python

Added 2026-03-12:
CAUTION! This gRPC Python release 1.78.1 was yanked from PyPI on 2026-02-26 due to issue #​41725.

  • [REVERTED] Remove unintentional log WARNING: All log messages before absl::InitializeLog() is called are written to STDERR. (#​41639)
  • [REVERTED] Fix inconsistent GRPC_ENABLE_FORK_SUPPORT runtime defaults between gRPC Core and Python. (#​41588).
    • This fixed #​37710, a request processing hang in certain multithreaded environments: Other threads are currently calling into gRPC, skipping fork() handlers.
  • Modernize the API Docs site: https://grpc.github.io/grpc/python. (#​41494)

Ruby

  • Build/test ruby 4.0 and build native gems with Ruby 4.0 support. (#​41554)
python/mypy (mypy)

v1.20.0

Compare Source

pytest-dev/pytest-cov (pytest-cov)

v7.1.0

Compare Source

  • Fixed total coverage computation to always be consistent, regardless of reporting settings.
    Previously some reports could produce different total counts, and consequently can make --cov-fail-under behave different depending on
    reporting options.
    See #&#8203;641 <https://github.com/pytest-dev/pytest-cov/issues/641>_.

  • Improve handling of ResourceWarning from sqlite3.

    The plugin adds warning filter for sqlite3 ResourceWarning unclosed database (since 6.2.0).
    It checks if there is already existing plugin for this message by comparing filter regular expression.
    When filter is specified on command line the message is escaped and does not match an expected message.
    A check for an escaped regular expression is added to handle this case.

    With this fix one can suppress ResourceWarning from sqlite3 from command line::

    pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...

  • Various improvements to documentation.
    Contributed by Art Pelling in #&#8203;718 <https://github.com/pytest-dev/pytest-cov/pull/718>_ and
    "vivodi" in #&#8203;738 <https://github.com/pytest-dev/pytest-cov/pull/738>.
    Also closed #&#8203;736 <https://github.com/pytest-dev/pytest-cov/issues/736>
    .

  • Fixed some assertions in tests.
    Contributed by in Markéta Machová in #&#8203;722 <https://github.com/pytest-dev/pytest-cov/pull/722>_.

  • Removed unnecessary coverage configuration copying (meant as a backup because reporting commands had configuration side-effects before coverage 5.0).

readthedocs/sphinx-autoapi (sphinx-autoapi)

v3.8.0

Compare Source

Features
^^^^^^^^

  • Autodoc-style directives can access members excluded by autoapi_options

Misc
^^^^


Configuration

📅 Schedule: (in timezone US/Central)

  • Branch creation
    • Only on Sunday (* * * * 0)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 7, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: packages/ni-grpc-extensions/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.datamonikers.v1.client/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.datamonikers.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.grpcdevice.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.discovery.v1.client/pyproject.toml
Artifact update for types-pywin32 resolved to version 311.0.0.20260408, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 311.0.0.20260323
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.discovery.v1.client/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.discovery.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.measurement.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.measurement.v2.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.pinmap.v1.client/pyproject.toml
Artifact update for types-pywin32 resolved to version 311.0.0.20260408, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 311.0.0.20260323
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.pinmap.v1.client/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.pinmap.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.sessionmanagement.v1.client/pyproject.toml
Artifact update for types-pywin32 resolved to version 311.0.0.20260408, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 311.0.0.20260323
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.sessionmanagement.v1.client/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurementlink.sessionmanagement.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurements.data.v1.client/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurements.data.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurements.metadata.v1.client/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.measurements.metadata.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.panels.v1.proto/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: packages/ni.protobuf.types/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/
File name: tools/grpc_generator/pyproject.toml
Artifact update for mypy resolved to version 1.20.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.20.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

Test Results

  120 files  ±0    120 suites  ±0   3m 27s ⏱️ ±0s
  251 tests ±0    249 ✅ ±0   2 💤 ±0  0 ❌ ±0 
2 510 runs  ±0  2 480 ✅ ±0  30 💤 ±0  0 ❌ ±0 

Results for commit 795b77b. ± Comparison against base commit de27af7.

♻️ This comment has been updated with latest results.

@renovate renovate bot force-pushed the users/renovate/python branch 6 times, most recently from 60d991e to 8951a0b Compare April 15, 2026 00:52
@renovate renovate bot force-pushed the users/renovate/python branch from 8951a0b to 795b77b Compare April 15, 2026 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants