Skip to content

fix(deps): update python dependencies#488

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

fix(deps): update python dependencies#488
renovate[bot] wants to merge 1 commit into8/edgefrom
renovate/python-dependencies

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
flake8 (changelog) 7.0.0 → 7.3.0 age confidence
jsonschema (changelog) 4.24.1 → 4.26.0 age confidence
lightkube ^0.15.3 → ^0.19.0 age confidence
ops (changelog) 2.21.1 → 2.23.2 age confidence
pep8-naming (changelog) ^0.13.3 → ^0.15.0 age confidence
pytest-asyncio (changelog) ^0.21.1 → ^0.26.0 age confidence
pytest-operator ^0.36.0 → ^0.43.0 age confidence
rpds-py 0.18.0 → 0.30.0 age confidence

Release Notes

pycqa/flake8 (flake8)

v7.3.0

Compare Source

v7.2.0

Compare Source

v7.1.2

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

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

canonical/operator (ops)

v2.23.2: : fix testing package build

Compare Source

What's Changed

This release fixes a recent build failure for ops[testing].

Fixes
  • Drop unused setuptools_scm build dependency in #​2318
Documentation
  • For 2.23, update links and config for switch to documentation.ubuntu.com/ops in #​1942
  • For 2.x, fix site title and unstyled error pages in #​1945
  • For 2.x, remove .html extensions in #​1954
  • For 2.x, fix unstyled error pages in #​1973

Full Changelog: canonical/operator@2.23.1...2.23.2

v2.23.1: : Add the remote unit to Relation.data, but not Relation.units

Compare Source

This is a small bug-fix release for the 2.x series that addresses issues with the recent feature making relation data available in relation-departed events. Rather than inserting the remote unit into Relation.units, the data is available from Relation.data, without changing Relation.units.

What's Changed

Fixes
  • Add the remote unit to Relation.data but not Relation.units in #​1928
Documentation
  • Be consistent with recommending self.app and self.unit in #​1856
  • Add notice about ops 2 and ops 3 in #​1867
  • Update title and edit links for ops 2.23 docs in #​1885
CI
  • Hotfix, publish job for ops-tracing in #​1865

Full Changelog: canonical/operator@2.23.0...2.23.1

v2.23.0

Compare Source

Features

  • Support for config schema as Python classes (#​1741)
  • Support for action parameter schema as Python classes (#​1756)
  • Ops[tracing] compatibility with jhack (#​1806)
  • Support for relation data schema as Python classes (#​1701)
  • Add CheckInfo.successes field and .has_run property (#​1819)
  • Provide a method to create a testing.State from a testing.Context (#​1797)
  • Expose trace data in testing (#​1842)
  • Add a helper to generate a Layer from rockcraft.yaml (#​1831)

Fixes

  • Correctly load an empty Juju config options map (#​1778)
  • Fix type annotation of container check_infos in ops.testing (#​1784)
  • Restrict the version of a dependency, opentelemetry-sdk (#​1794)
  • Remote unit data is available in relation-departed (#​1364)
  • Juju allows access to the remote app databag in relation-broken, so Harness should too (#​1787)
  • Don't use private OpenTelemetry API (#​1798)
  • Do not return this unit in a mocked peer relation (#​1828)
  • Testing.PeerRelation properly defaults to no peers (#​1832)
  • In meter-status-changed JUJU_VERSION is not set (#​1840)
  • Only provide the units belonging to the app in Relation.units (#​1837)

Documentation

  • Remove two best practices, and drop two to tips (#​1758)
  • Update link to Charmcraft for managing app config (#​1763)
  • Update link to Juju documentation for setting up deployment (#​1781)
  • Fix external OTLP link (#​1786)
  • Distribute the ops-scenario README content across the ops docs (#​1773)
  • Improve testing.errors.UncaughtCharmError message (#​1795)
  • In the "manage the charm version" how-to, give an example of using override-build (#​1802)
  • Small adjustments to the 'how to trace charm code' doc (#​1792)
  • Replace Harness example and fix links in README (#​1820)
  • Add httpbin charm from Charmcraft as an example charm (#​1743)
  • Fix on_collect mistake in sample code (#​1829)
  • Update code in K8s tutorial, with source in repo (part 2) (#​1734)
  • Update Loki section on charming zero-to-hero tutorial (#​1847)
  • Remove expandable boxes of text (#​1844)
  • Improve httpbin charm by removing defer() and adding collect_status (#​1833)
  • Move {posargs} to the end of pytest command lines in tox.ini (#​1854)

CI

  • Install the ops[tracing] dependencies for the TIOBE action (#​1761)
  • Add ops-scenario and ops-tracing as explicit installs for TIOBE (#​1764)
  • Persist credentials for update-charm-pins workflow (#​1766)
  • Stop smoke testing Charmcraft 2 (#​1782)
  • Use Charmcraft 3.x for smoke testing 20.04 and 22.04 (#​1821)
  • Enable xdist for the 'unit' tox environments (#​1830)

v2.22.0

Compare Source

Features

Fixes

  • Turn on databag access validation in __init__ (#​1737)
  • Allow event suffixes to appear in event names in ops.testing (#​1754)

Documentation

  • Document how to manage metrics (#​1692)
  • Link to our docs from the top of our README (#​1710)
  • Update code in K8s tutorial, with source in repo (part 1) (#​1719)
  • Update links to juju.is/docs (#​1725)
  • Fix link in breakpoint output, remove link from Harness error message (#​1726)
  • Update Matrix channel name to Charm Tech (#​1740)
  • Rename configurations to configuration (#​1746)
  • Fix typos in code snippets by @​MattiaSarti (#​1750)

CI

  • Add ops[tracing] integration tests (#​1686)
  • Pin workflows by hash (#​1721)
  • Disable alertmanager compatibility tests until upstream fix (#​1745)
  • Remove explicit scopes and update HACKING.md (#​1748)
  • Pin trusted workflows by tag (#​1752)
  • Re-enable alertmanager-k8s-operator in observability charm tests (#​1753)
  • Fix reporting to TIOBE after ops[tracing] addition (#​1755)
PyCQA/pep8-naming (pep8-naming)

v0.15.1

Compare Source

  • N808 now allows type variable names to start with an underscore.

v0.15.0

Compare Source

  • Add support for Python 3.13.
  • Drop support for Python 3.8.
  • N808 checks type variable names use the CapWords convention and have an appropriate suffix.

v0.14.1

Compare Source

  • Require Python 3.8 or later.

v0.14.0

Compare Source

  • Drop support for Python 3.7.
  • Add support for Python 3.12.
  • Ignore methods decorated by @typing.override.
  • Perform case-sensitive ignore-names globbing on all platforms.
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.43.2

Compare Source

What's Changed

  • fix: cloud entries in an dictionary were being deleted while iterating the object by @​addyess in #​155

Full Changelog: charmed-kubernetes/pytest-operator@v0.43.1...v0.43.2

v0.43.1

Compare Source

What's Changed

  • fix: Allow for pytest to be run with overridden --basetemp argument by @​addyess in #​153

Full Changelog: charmed-kubernetes/pytest-operator@v0.43.0...v0.43.1

v0.43.0

Compare Source

What's Changed

Full Changelog: charmed-kubernetes/pytest-operator@v0.42.1...v0.43.0

v0.42.1

Compare Source

v0.42.0

Compare Source

v0.41.0

What's Changed

Full Changelog: charmed-kubernetes/pytest-operator@v0.39.0...v0.41.0

v0.37.0: 0.37.0

Compare Source

crate-py/rpds (rpds-py)

v0.30.0

Compare Source

What's Changed

Full Changelog: crate-py/rpds@v0.29.0...v0.30.0

v0.29.0

Compare Source

What's Changed

Full Changelog: crate-py/rpds@v0.28.0...v0.29.0

v0.28.0

Compare Source

What's Changed

  • Bump PyO3 to 0.27

Full Changelog: crate-py/rpds@v0.27.1...v0.28.0

v0.27.1

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.27.0...v0.27.1

v0.27.0

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.26.0...v0.27.0

v0.26.0

Compare Source

What's Changed

Full Changelog: crate-py/rpds@v0.25.1...v0.26.0

v0.25.1

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.25.0...v0.25.1

v0.25.0

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.24.0...v0.25.0

v0.24.0

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.23.1...v0.24.0

v0.23.1

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.23.0...v0.23.1

v0.23.0

Compare Source

Full Changelog: crate-py/rpds@v0.22.3...v0.23.0

v0.22.3

Compare Source

Full Changelog: crate-py/rpds@v0.22.2...v0.22.3

v0.22.1

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.22.0...v0.22.1

v0.22.0

Compare Source

What's Changed

New Contributors

Full Changelog: crate-py/rpds@v0.21.0...v0.22.0

v0.21.0

Compare Source

What's Changed

New Contributors

Configuration

📅 Schedule: Branch creation - "after 1am and before 2am every weekday" in timezone Etc/UTC, 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.

@renovate
Copy link
Contributor Author

renovate bot commented Jan 19, 2026

⚠️ 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...

Creating virtualenv non-package-mode-TPm3349i-py3.14 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because no versions of pytest-operator match >0.43.0,<0.43.1 || >0.43.1,<0.43.2 || >0.43.2,<0.44.0
 and pytest-operator (0.43.0) depends on pytest-asyncio (<0.23), pytest-operator (>=0.43.0,<0.43.1 || >0.43.1,<0.43.2 || >0.43.2,<0.44.0) requires pytest-asyncio (<0.23).
And because pytest-operator (0.43.1) depends on pytest-asyncio (<0.23)
 and pytest-operator (0.43.2) depends on pytest-asyncio (<0.23), pytest-operator (>=0.43.0,<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.0), version solving failed.

@renovate renovate bot force-pushed the renovate/python-dependencies branch 6 times, most recently from c6f7dfb to fc0e016 Compare January 29, 2026 13:53
@renovate renovate bot force-pushed the renovate/python-dependencies branch 6 times, most recently from c3499c6 to 1c511eb Compare February 9, 2026 15:53
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 1c511eb to 4b4492a Compare February 10, 2026 07:48
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants