Skip to content

Update Python dependencies#168

Open
renovate[bot] wants to merge 1 commit into8/edgefrom
renovate/python-dependencies
Open

Update Python dependencies#168
renovate[bot] wants to merge 1 commit into8/edgefrom
renovate/python-dependencies

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 20, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
allure-pytest (source) ^2.13.5 → ^2.15.3 age confidence
cffi (changelog) ^1.16.0 → ^1.17.1 age confidence
charm-refresh-build-version ^0.4.0 → ^0.4.1 age confidence
codespell ^2.2.6 → ^2.4.2 age confidence
jinja2 (changelog) ^3.1.3 → ^3.1.6 age confidence
jsonschema (changelog) 4.24.1 → 4.26.0 age confidence
lightkube ^0.15.3 → ^0.19.1 age confidence
ops (changelog) >=2.21 → >=2.23.2 age confidence
poetry-core ^2.0 → ^2.3.2 age confidence
pydantic (changelog) 2.11.10 → 2.13.3 age confidence
pymongo ^4.7.3 → ^4.17.0 age confidence
pytest-asyncio (changelog) ^0.21.1 → ^0.26.0 age confidence
pytest-operator ^0.34.0 → ^0.43.2 age confidence
pyyaml (source) ^6.0.1 → ^6.0.3 age confidence
rpds-py 0.18.0 → 0.30.0 age confidence
ruff (source, changelog) ^0.1.6 → ^0.15.11 age confidence

Release Notes

python-jsonschema/jsonschema (jsonschema)

v4.26.0

Compare Source

=======

  • Decrease import time by delaying importing of urllib.request (#​1416).

v4.25.1

Compare Source

=======

  • Fix an incorrect required argument in the Validator protocol's type annotations (#​1396).

v4.25.0

Compare Source

=======

  • Add support for the iri and iri-reference formats to the format-nongpl extra via the MIT-licensed rfc3987-syntax.
    They were alread supported by the format extra. (#​1388).
gtsystem/lightkube (lightkube)

v0.19.1

Compare Source

v0.19.0

Compare Source

What's Changed

Full Changelog: gtsystem/lightkube@v0.18.0...v0.19.0

v0.18.0

Compare Source

What's Changed
Bug fix
Typing improvements
New Contributors

Full Changelog: gtsystem/lightkube@v0.17.2...v0.18.0

v0.17.2

Compare Source

What's Changed
New Contributors

Full Changelog: gtsystem/lightkube@v0.17.0...v0.17.2

v0.17.1

Compare Source

v0.17.0

Compare Source

New features
  • client.list() now returns an iterable with a special property resourceVersion to implement list + watch pattern by @​XeCycle in #​88
Bug fixes
Breaking changes
  • As part of the new feature above, client.list() now returns an Iteratable instead of an Iterator. If you are consuming the list using next() you will need to get an iterator first calling iter(list). No changes are needed If you are consuming the returned data via a for loop.

Full Changelog: gtsystem/lightkube@v0.16.0...v0.17.0

v0.16.2

Compare Source

v0.16.1

Compare Source

v0.16.0

Compare Source

What's Changed
Bug fixes
  • #​78: Limit max httpx version to < 0.28.0 as 0.28.0 introduces a not documented breaking change by @​gtsystem in #​81
  • When loading kubeconfig files configured with ExecCredential, lightkube now accepts the env parameter when set to null explicitly (Azure kubelogin compatiblity) by @​raminqaf in #​80
New Contributors

Full Changelog: gtsystem/lightkube@v0.15.4...v0.16.0

v0.15.8

Compare Source

v0.15.7

Compare Source

pydantic/pydantic (pydantic)

v2.13.3

Compare Source

GitHub release

What's Changed
Fixes

v2.13.2

Compare Source

v2.13.1: 2026-04-15

Compare Source

v2.13.1 (2026-04-15)

What's Changed
Fixes

Full Changelog: pydantic/pydantic@v2.13.0...v2.13.1

v2.13.0

Compare Source

GitHub release

The highlights of the v2.13 release are available in the blog post.
Several minor changes (considered non-breaking changes according to our versioning policy)
are also included in this release. Make sure to look into them before upgrading.

This release contains the updated pydantic.v1 namespace, matching version 1.10.26 which includes support for Python 3.14.

What's Changed

See the beta releases for all changes sinces 2.12.

New Features
  • Allow default factories of private attributes to take validated model data by @​Viicos in #​13013
Changes
Fixes
  • Change type of Any when synthesizing _build_sources for BaseSettings.__init__() signature in the mypy plugin by @​Viicos in #​13049
  • Fix model equality when using runtime extra configuration by @​Viicos in #​13062
Packaging
New Contributors

v2.12.5: 2025-11-26

Compare Source

v2.12.5 (2025-11-26)

This is the fifth 2.12 patch release, addressing an issue with the MISSING sentinel and providing several documentation improvements.

The next 2.13 minor release will be published in a couple weeks, and will include a new polymorphic serialization feature addressing
the remaining unexpected changes to the serialize as any behavior.

  • Fix pickle error when using model_construct() on a model with MISSING as a default value by @​ornariece in #​12522.
  • Several updates to the documentation by @​Viicos.

Full Changelog: pydantic/pydantic@v2.12.4...v2.12.5

v2.12.4

Compare Source

v2.12.3

Compare Source

GitHub release

What's Changed

This is the third 2.13 patch release, fixing issues related to the FieldInfo class, and reverting a change to the supported
after model validator function signatures.

  • Raise a warning when an invalid after model validator function signature is raised by @​Viicos in #​12414.
    Starting in 2.12.0, using class methods for after model validators raised an error, but the error wasn't raised concistently. We decided
    to emit a deprecation warning instead.
  • Add FieldInfo.asdict() method, improve documentation around FieldInfo by @​Viicos in #​12411.
    This also add back support for mutations on FieldInfo classes, that are reused as Annotated metadata. However, note that this is still
    not a supported pattern. Instead, please refer to the added example in the documentation.

The blog post section on changes was also updated to document the changes related to serialize_as_any.

v2.12.2

Compare Source

GitHub release

What's Changed
Fixes
  • Release a new pydantic-core version, as a corrupted CPython 3.10 manylinux2014_aarch64 wheel got uploaded (pydantic-core#1843).
  • Fix issue with recursive generic models with a parent model class by @​Viicos in #​12398

v2.12.1

Compare Source

GitHub release

What's Changed

This is the first 2.12 patch release, addressing most (but not all yet) regressions from the initial 2.12.0 release.

Fixes
New Contributors

v2.12.0

Compare Source

GitHub release

What's Changed

This is the final 2.12 release. It features the work of 20 external contributors and provides useful new features, along with initial Python 3.14 support.
Several minor changes (considered non-breaking changes according to our versioning policy)
are also included in this release. Make sure to look into them before upgrading.

Note that Pydantic V1 is not compatible with Python 3.14 and greater.

Changes (see the alpha and beta releases for additional changes since 2.11):

Packaging
New Features
Fixes
New Contributors
mongodb/mongo-python-driver (pymongo)

v4.17.0: PyMongo 4.17.0

Compare Source

Community notes:

What's Changed

New Contributors

Full Changelog: mongodb/mongo-python-driver@4.16.0...4.17.0

pytest-dev/pytest-asyncio (pytest-asyncio)

v0.26.0: pytest-asyncio 0.26.0

Compare Source

  • Adds configuration option that sets default event loop scope for all tests #​793
  • Improved type annotations for pytest_asyncio.fixture #​1045
  • Added typing-extensions as additional dependency for Python <3.10 #​1045

v0.25.3: pytest-asyncio 0.25.3

Compare Source

  • Avoid errors in cleanup of async generators when event loop is already closed #​1040

v0.25.2: pytest-asyncio 0.25.2

Compare Source

  • Call loop.shutdown_asyncgens() before closing the event loop to ensure async generators are closed in the same manner as asyncio.run does #​1034

v0.25.1: pytest-asyncio 0.25.1

Compare Source

  • Fixes an issue that caused a broken event loop when a function-scoped test was executed in between two tests with wider loop scope #​950
  • Improves test collection speed in auto mode #​1020
  • Corrects the warning that is emitted upon redefining the event_loop fixture

v0.25.0: pytest-asyncio 0.25.0

Compare Source

0.25.0 (2024-12-13)

  • Deprecated: Added warning when asyncio test requests async @pytest.fixture in strict mode. This will become an error in a future version of flake8-asyncio. #​979
  • Updates the error message about pytest.mark.asyncio's scope keyword argument to say loop_scope instead. #​1004
  • Verbose log displays correct parameter name: asyncio_default_fixture_loop_scope #​990
  • Propagates contextvars set in async fixtures to other fixtures and tests on Python 3.11 and above. #​1008

v0.24.0: pytest-asyncio 0.24.0

Compare Source

0.24.0 (2024-08-22)

  • BREAKING: Updated minimum supported pytest version to v8.2.0
  • Adds an optional loop_scope keyword argument to pytest.mark.asyncio. This argument controls which event loop is used to run the marked async test. #​706, #​871
  • Deprecates the optional scope keyword argument to pytest.mark.asyncio for API consistency with pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.
  • Raises an error when passing scope or loop_scope as a positional argument to @pytest.mark.asyncio. #​812
  • Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules #​862 #​668

v0.23.8: pytest-asyncio 0.23.8

Compare Source

0.23.8 (2024-07-17)

  • Fixes a bug that caused duplicate markers in async tests #​813

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #​706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

v0.23.7: pytest-asyncio 0.23.7

Compare Source

0.23.7 (2024-05-19)

  • Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases #​817

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #​706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

v0.23.6: pytest-asyncio 0.23.6

Compare Source

0.23.6 (2024-03-19)

  • Fix compatibility with pytest 8.2 #​800

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #​706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

v0.23.5: pytest-asyncio 0.23.5

Compare Source

0.23.5 (2024-02-09)

  • Declare compatibility with pytest 8 #​737
  • Fix typing errors with recent versions of mypy #​769
  • Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #​757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #​706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

v0.23.4: pytest-asyncio 0.23.4

Compare Source

0.23.4 (2024-01-28)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #​729
  • Addresses further issues that caused an internal pytest error during test collection
  • Declares incompatibility with pytest 8 #​737

v0.23.3: pytest-asyncio 0.23.3

Compare Source

0.23.3 (2024-01-01)

  • Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #​706
  • Fixes various bugs that caused an internal pytest error during test collection #​711 #​713 #​719

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #​706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

v0.23.2: pytest-asyncio 0.23.2

Compare Source

0.23.2 (2023-12-04)

  • Fixes a bug that caused an internal pytest error when collecting .txt files #​703

v0.23.1: pytest-asyncio 0.23.1

Compare Source

0.23.1 (2023-12-03)

  • Fixes a bug that caused an internal pytest error when using module-level skips #​701

v0.23.0: pytest-asyncio 0.23.0

Compare Source

This release is backwards-compatible with v0.21. Changes are
non-breaking, unless you upgrade from v0.22.

  • BREAKING: The asyncio_event_loop mark has been removed. Event
    loops with class, module, package, and session scopes can be
    requested via the scope keyword argument to the asyncio
    mark.
  • Introduces the event_loop_policy fixture which allows testing with
    non-default or multiple event loops #​662
  • Introduces pytest_asyncio.is_async_test which returns whether a
    test item is managed by pytest-asyncio #​376
  • Removes and pytest-trio, mypy, and flaky from the test
    dependencies #​620, #​674, #​678

v0.22.0: pytest-asyncio 0.22.0 (yanked)

Compare Source

This release deprecated event loop overrides, but didn't provide adequate replacement functionality for all relevant use cases. As such, the release was yanked from PyPI.

0.22.0 (2023-10-31)

  • Class-scoped and module-scoped event loops can be requested
    via the asyncio_event_loop mark. #​620
  • Deprecate redefinition of the event_loop fixture. #​587
    Users requiring a class-scoped or module-scoped asyncio event loop for their tests
    should mark the corresponding class or module with asyncio_event_loop.
  • Test items based on asynchronous generators always exit with xfail status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. #​642
  • Remove support for Python 3.7
  • Declare support for Python 3.12
charmed-kubernetes/pytest-operator (pytest-operator)

[`v0.

@renovate renovate Bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Jan 20, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jan 20, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact 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: poetry.lock
Updating dependencies
Resolving dependencies...


Because no versions of pytest-operator match >0.43.2,<0.44.0
 and pytest-operator (0.43.2) depends on pytest-asyncio (<0.23), pytest-operator (>=0.43.2,<0.44.0) requires pytest-asyncio (<0.23).
So, because non-package-mode depends on both pytest-asyncio (^0.26.0) and pytest-operator (^0.43.2), version solving failed.

@renovate renovate Bot force-pushed the renovate/python-dependencies branch from c1aa573 to c8cf10d Compare January 27, 2026 02:08
@renovate renovate Bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 4528e70 to f562d2d Compare February 10, 2026 02:02
@renovate renovate Bot force-pushed the renovate/python-dependencies branch from f562d2d to a9f0910 Compare February 17, 2026 01:55
@renovate renovate Bot changed the title Lock file maintenance Python dependencies Update Python dependencies Feb 17, 2026
@renovate renovate Bot force-pushed the renovate/python-dependencies branch 2 times, most recently from e47ad4c to 512cb92 Compare March 3, 2026 01:53
@renovate renovate Bot force-pushed the renovate/python-dependencies branch from 512cb92 to ea74e99 Compare March 10, 2026 01:52
@renovate renovate Bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 9f1894f to 052efd9 Compare March 24, 2026 01:47
@renovate renovate Bot force-pushed the renovate/python-dependencies branch from 052efd9 to bab1fcf Compare March 31, 2026 01:44
@renovate renovate Bot force-pushed the renovate/python-dependencies branch from bab1fcf to b4f4141 Compare April 7, 2026 01:57
@renovate renovate Bot force-pushed the renovate/python-dependencies branch from b4f4141 to 0155f82 Compare April 14, 2026 02:10
@renovate renovate Bot force-pushed the renovate/python-dependencies branch from 0155f82 to f044290 Compare April 21, 2026 03:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants