Lock file maintenance Python dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
		lockFileMaintenance	All locks refreshed
cffi (source, changelog)	dependencies	patch	^1.16.0 -> ^1.17.1
codespell	lint	patch	^2.2.6 -> ^2.3.0
coverage	unit	patch	^7.5.0 -> ^7.6.10
ops (changelog)	integration	minor	~2.15.0 -> ~2.17.1
ops (changelog)	dependencies	minor	~2.15.0 -> ~2.17.1
poetry-core	dependencies	patch	^1.9.0 -> ^1.9.1
pyOpenSSL (source)	dependencies	minor	^24.2.1 -> ^24.3.0
pydantic (changelog)	charm-libs	patch	1.10.18 -> 1.10.19
pymongo	integration	patch	^4.7.3 -> ^4.10.1
pymongo	unit	patch	^4.7.3 -> ^4.10.1
pymongo	dependencies	patch	^4.7.3 -> ^4.10.1
pytest (changelog)	integration	patch	^8.1.1 -> ^8.3.4
pytest (changelog)	unit	patch	^8.1.1 -> ^8.3.4
pytest-asyncio (changelog)	integration	minor	^0.21.1 -> ^0.25.1
pytest-operator	integration	minor	^0.34.0 -> ^0.39.0
pyyaml (source)	dependencies	patch	^6.0.1 -> ^6.0.2
rpds-py	dependencies	minor	0.18.0 -> 0.22.3
ruff (source, changelog)	lint	minor	^0.1.6 -> ^0.8.5
ruff (source, changelog)	format	minor	^0.1.6 -> ^0.8.5
tenacity	integration	patch	^8.2.3 -> ^8.5.0
tenacity	dependencies	patch	^8.2.3 -> ^8.5.0

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Release Notes

nedbat/coveragepy (coverage)

v7.6.10

Compare Source

• Fix: some descriptions of missing branches in HTML and LCOV reports were
  incorrect when multi-line statements were involved (issue 1874_ and issue 1875_). These are now fixed.

• Fix: Python 3.14 defers evaluation of annotations <pep649_>_ by moving them
  into separate code objects. That code is rarely executed, so coverage.py
  would mark them as missing, as reported in issue 1908_. Now they are
  ignored by coverage automatically.

• Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
  mocks, imports, and trace functions: issue 1902_. To be honest, I don't
  understand the problem or the solution, but git bisect helped find it,
  and now it's fixed.

• Docs: re-wrote the :ref:subprocess page to put multiprocessing first and to
  highlight the correct use of :class:multiprocessing.Pool <python:multiprocessing.pool.Pool>.

.. _issue 1874:https://github.com/nedbat/coveragepy/issues/18744
.. _issue 1875https://github.com/nedbat/coveragepy/issues/187575
.. _issue 190https://github.com/nedbat/coveragepy/issues/1902902
.. _issue 19https://github.com/nedbat/coveragepy/issues/19081908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#pep-649-deferred-evaluation-of-annotations

.. _changes_7-6-9:

v7.6.9

Compare Source

• Fix: Tomas Uribe fixed <pull 1901_>_ a performance problem in the XML
  report. Large code bases should produce XML reports much faster now.

.. _pull 1901:https://github.com/nedbat/coveragepy/pull/19011

.. _changes_7-6-8:

v7.6.8

Compare Source

• Fix: the LCOV report code assumed that a branch line that took no branches
  meant that the entire line was unexecuted. This isn't true in a few cases:
  the line might always raise an exception, or might have been optimized away.
  Fixes issue 1896_.

• Fix: similarly, the HTML report will now explain that a line that jumps to
  none of its expected destinations must have always raised an exception.
  Previously, it would say something nonsensical like, "line 4 didn't jump to
  line 5 because line 4 was never true, and it didn't jump to line 7 because
  line 4 was always true." This was also shown in issue 1896_.

.. _issue 1896:https://github.com/nedbat/coveragepy/issues/18966

.. _changes_7-6-7:

v7.6.7

Compare Source

• fix: ugh, the other assert from 7.6.5 can also be encountered in the wild,
  so it's been restored to a conditional. Sorry for the churn.

.. _changes_7-6-6:

v7.6.6

Compare Source

• One of the new asserts from 7.6.5 caused problems in real projects, as
  reported in issue 1891_. The assert has been removed.

.. _issue 1891:https://github.com/nedbat/coveragepy/issues/18911

.. _changes_7-6-5:

v7.6.5

Compare Source

• fix: fine-tuned the exact Python version (3.12.6) when exiting from with
  statements changed how they traced. This affected whether people saw the
  fix for issue 1880_.

• fix: isolate our code more from mocking in the os module that in rare cases
  can cause bizarre behavior <pytest-cov-666_>_.

• refactor: some code unreachable code paths in parser.py were changed to
  asserts. If you encounter any of these, please let me know!

.. _pytest-cov-666:https://github.com/pytest-dev/pytest-cov/issues/6666

.. _changes_7-6-4:

v7.6.4

Compare Source

• fix: multi-line with statements could cause contained branches to be
  incorrectly marked as missing (issue 1880_). This is now fixed.

.. _issue 1880:https://github.com/nedbat/coveragepy/issues/18800

.. _changes_7-6-3:

v7.6.3

Compare Source

• Fix: nested context managers could incorrectly be analyzed to flag a missing
  branch on the last context manager, as described in issue 1876_. This is
  now fixed.

• Fix: the missing branch message about not exiting a module had an extra
  "didn't," as described in issue 1873_. This is now fixed.

.. _issue 1873:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676

.. _changes_7-6-2:

v7.6.2

Compare Source

• Dropped support for Python 3.8 and PyPy 3.8.

• Fix: a final wildcard match/case clause assigning to a name (case _ as value) was incorrectly marked as a missing branch. This is now fixed,
  closing issue 1860_.

• Fewer things are considered branches now. Lambdas, comprehensions, and
  generator expressions are no longer marked as missing branches if they don't
  complete execution. Closes issue 1852_.

• Fix: the HTML report didn't properly show multi-line f-strings that end with
  a backslash continuation. This is now fixed, closing issue 1836, thanks
  to LiuYinCarl and Marco Ricci <pull 1838_>.

• Fix: the LCOV report now has correct line numbers (fixing issue 1846) and
  better branch descriptions for BRDA records (fixing issue 1850). There
  are other changes to lcov also, including a new configuration option
  :ref:line_checksums <config_lcov_line_checksums> to control whether line
  checksums are included in the lcov report. The default is false. To keep
  checksums set it to true. All this work is thanks to Zack Weinberg
  (pull 1849_ and pull 1851_).

• Fixed the docs for multi-line regex exclusions, closing issue 1863_.

• Fixed a potential crash in the C tracer, closing issue 1835, thanks to
  Jan Kühle <pull 1843_>.

.. _issue 1835:https://github.com/nedbat/coveragepy/issues/18355
.. _issue 1836https://github.com/nedbat/coveragepy/issues/183636
.. _pull 183https://github.com/nedbat/coveragepy/pull/1838838
.. _pull 18https://github.com/nedbat/coveragepy/pull/18431843
.. _issue 1https://github.com/nedbat/coveragepy/issues/1846/1846
.. _pull https://github.com/nedbat/coveragepy/pull/1849l/1849
.. _issuehttps://github.com/nedbat/coveragepy/issues/1850es/1850
.. _pulhttps://github.com/nedbat/coveragepy/pull/1851ull/1851
.. _isshttps://github.com/nedbat/coveragepy/issues/1852sues/1852
.. _ishttps://github.com/nedbat/coveragepy/issues/1860ssues/1860
.. _ihttps://github.com/nedbat/coveragepy/issues/1863issues/1863

.. _changes_7-6-1:

canonical/operator (ops)

v2.17.1

Compare Source

Fixes

• Make push_path open in binary mode so it works on non-text files (#​1458)

Documentation

• Use MaintenanceStatus for local issues (#​1397)
• Explicitly document that collect-status is is run on every hook (#​1399)
• Use our docs URL for the ogp:url properties Sphinx generates (#​1411)
• Set the READTHEDOCS context variable (#​1410)
• Fix Read the Docs ad placement (#​1414)
• Clarify where StoredState is stored, and the upgrade behaviour (#​1416)
• Fix copy 'n' paste error in stop_services docstring (#​1457)

Continuous Integration

• Configure the labels for dependabot PRs (#​1407)
• Disable the automatic ops[testing] releasing (#​1415)
• Use the actual poetry command, rather than manually tweaking the file (#​1443)
• Fix broken GitHub variable expansion (#​1446)
• Coverage report generation should also include testing/src/scenario (#​1453)
• Fix PR title CI job concurrency (#​1451)
• Adjust the release process to handle publishing ops and ops[testing] (#​1432)
• A better way than commenting out external repos (#​1463)
• Use more descriptive names for the publish workflows (#​1464)
• Move the XML coverage report to .report (#​1465)

Refactoring

• Import the ops[testing] repository (#​1406)
• Update linting with the latest ruff (#​1441)

v2.17.0

Compare Source

Features

• Optionally install Scenario with ops[testing] and expose the names in ops.testing (#​1381)
• Change ops.main() so that you don't need to type: ignore it (#​1345)
• Expand the secret ID out to the full URI when only given the ID (#​1358)
• Add a JujuVersion property for Pebble log forwarding to Loki (#​1370)
• Pre-emptively raise InvalidStatusError instead of waiting for Juju:
  • Make it an error to call CollectStatusEvent.add_status with error or unknown (#​1386)
  • Document and validate settable status values in _ModelBackend.set_status (#​1354)

Fixes

• Fix type of StatusBase subclasses by calling StatusBase.register in __init_subclass__ (#​1383)
• Secret.set_info and Secret.set_content can be called in the same hook (#​1373)

Documentation

• Add top-level intro and module-level intros (#​1320)
• Update the links to the Pebble docs (#​1362)
• Note about repeatedly setting secret value in Juju 3.6 (#​1366)
• config-changed is triggered by Juju trust (#​1357)
• Typo on CharmBase inheritance example by @​theofpa (#​1349)
• Docs: move Pebble to a separate page (#​1392)

Continuous Integration

• Periodically run the unit tests of all GitHub-hosted published charms (#​1365)
• Update the TIOBE reporting for the changes in coverage calculation (#​1367)
• Spell-check the code as part of linting (#​1388)
• Run the smoke tests on a schedule (#​1387)

Testing

• Fix tests that leaked environment variables (#​1385)

Refactoring

• Move the content of ops.testing to ops._private.harness (#​1369)
• Keep the unittest.mock names in the 'mock' namespace (#​1379)
• Deprecate StatusBase.register decorator (#​1384)

Chores

• Note Juju version on legacy workaround (#​1355)
• Re-enable test now that Pebble directory permissions are fixed (#​1363)
• Generate warnings for events that will be removed in Juju 4.0 (#​1374)

v2.16.1

Compare Source

Fix

• Don't alter os.environ when creating a Harness (#​1359)

v2.16.0

Compare Source

Features

• Add the description field to SecretInfo in (#​1338)

Refactor

• Parse JUJU_* environment variables in one place in (#​1313)

Fixes

• Fix reading Juju secret expiry dates in (#​1317)
• Correct the signature of .events() in (#​1342)

Documentation

• Security policy change to only support each active major release in (#​1297)
• Add Juju version markers in (#​1311)
• Use Sphinx 8 in (#​1303)
• Live reload documentation with sphinx-autobuild in (#​1323)

Tests

• Update the smoke test series/bases in (#​1318)
• Run pytest in parallel with pytest xdist in (#​1319)
• Bump Pyright to 1.1.377 in (#​1332)
• Run tests on Python 3.12 and the install test on Python 3.13 in (#​1315)

CI

• Add a workflow that runs the TIOBE quality checks in (#​1301)
• Allow executing the TIOBE workflow manually in (#​1321)
• Make Pyright report unnecessary type ignore comments in (#​1333)
• Enable linting of docs/custom_conf.py in (#​1330)

python-poetry/poetry-core (poetry-core)

v1.9.1

Compare Source

Added

• Add 3.13 to the list of available Python versions (#​747).

pyca/pyopenssl (pyOpenSSL)

v24.3.0

Compare Source

Backward-incompatible changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Removed the deprecated OpenSSL.crypto.CRL, OpenSSL.crypto.Revoked, OpenSSL.crypto.dump_crl, and OpenSSL.crypto.load_crl. cryptography.x509's CRL functionality should be used instead.
• Removed the deprecated OpenSSL.crypto.sign and OpenSSL.crypto.verify. cryptography.hazmat.primitives.asymmetric's signature APIs should be used instead.

Deprecations:
^^^^^^^^^^^^^

• Deprecated OpenSSL.rand - callers should use os.urandom() instead.
• Deprecated add_extensions and get_extensions on OpenSSL.crypto.X509Req and OpenSSL.crypto.X509. These should have been deprecated at the same time X509Extension was. Users should use pyca/cryptography's X.509 APIs instead.
• Deprecated OpenSSL.crypto.get_elliptic_curves and OpenSSL.crypto.get_elliptic_curve, as well as passing the reult of them to OpenSSL.SSL.Context.set_tmp_ecdh, users should instead pass curves from cryptography.
• Deprecated passing X509 objects to OpenSSL.SSL.Context.use_certificate, OpenSSL.SSL.Connection.use_certificate, OpenSSL.SSL.Context.add_extra_chain_cert, and OpenSSL.SSL.Context.add_client_ca, users should instead pass cryptography.x509.Certificate instances. This is in preparation for deprecating pyOpenSSL's X509 entirely.
• Deprecated passing PKey objects to OpenSSL.SSL.Context.use_privatekey and OpenSSL.SSL.Connection.use_privatekey, users should instead pass cryptography priate key instances. This is in preparation for deprecating pyOpenSSL's PKey entirely.

Changes:
^^^^^^^^

• cryptography maximum version has been increased to 44.0.x.
• OpenSSL.SSL.Connection.get_certificate, OpenSSL.SSL.Connection.get_peer_certificate, OpenSSL.SSL.Connection.get_peer_cert_chain, and OpenSSL.SSL.Connection.get_verified_chain now take an as_cryptography keyword-argument. When True is passed then cryptography.x509.Certificate are returned, instead of OpenSSL.crypto.X509. In the future, passing False (the default) will be deprecated.

pydantic/pydantic (pydantic)

v1.10.19

Compare Source

• Add warning when v2 model is nested in v1 model by @​sydney-runkle in https://github.com/pydantic/pydantic/pull/10432
• Fix deprecation warning in V1 isinstance check by @​alicederyn in https://github.com/pydantic/pydantic/pull/10645

pytest-dev/pytest (pytest)

v8.3.4

Compare Source

pytest 8.3.4 (2024-12-01)

Bug fixes

• #​12592: Fixed KeyError{.interpreted-text role="class"} crash when using --import-mode=importlib in a directory layout where a directory contains a child directory with the same name.

• #​12818: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the AST, like executing.

• #​12849: ANSI escape codes for colored output now handled correctly in pytest.fail{.interpreted-text role="func"} with [pytrace=False]{.title-ref}.

• #​9353: pytest.approx{.interpreted-text role="func"} now uses strict equality when given booleans.

Improved documentation

• #​10558: Fix ambiguous docstring of pytest.Config.getoption{.interpreted-text role="func"}.

• #​10829: Improve documentation on the current handling of the --basetemp option and its lack of retention functionality (temporary directory location and retention{.interpreted-text role="ref"}).

• #​12866: Improved cross-references concerning the recwarn{.interpreted-text role="fixture"} fixture.

• #​12966: Clarify filterwarnings{.interpreted-text role="ref"} docs on filter precedence/order when using multiple @pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>{.interpreted-text role="ref"} marks.

Contributor-facing changes

• #​12497: Fixed two failing pdb-related tests on Python 3.13.

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

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.37.0: 0.37.0

Compare Source

crate-py/rpds (rpds-py)

v0.22.3

Compare Source

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

v0.22.1

Compare Source

What's Changed

• ci: separate free-threaded and standard 3.13 distribution builds by @​RobPasMue in https://github.com/crate-py/rpds/pull/111

New Contributors

• @​RobPasMue made their first contribution in https://github.com/crate-py/rpds/pull/111

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

v0.22.0

Compare Source

What's Changed

• update rpds.py for PyO3 0.23 by @​ngoldbaum in https://github.com/crate-py/rpds/pull/100
• Declare free-threading support by @​ngoldbaum in https://github.com/crate-py/rpds/pull/104
• Enable free-threaded wheel builds by @​ngoldbaum in https://github.com/crate-py/rpds/pull/107

New Contributors

• @​ngoldbaum made their first contribution in https://github.com/crate-py/rpds/pull/100

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

v0.21.0

Compare Source

What's Changed

• bump pyO3 to 0.22.6 by @​minrk in https://github.com/crate-py/rpds/pull/97

New Contributors

• @​minrk made their first contribution in https://github.com/crate-py/rpds/pull/97

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

v0.20.1

Compare Source

What's Changed

• Fix hashing overflow issues (#​86) by @​FlickerSoul in https://github.com/crate-py/rpds/pull/87

Full Changelog: crate-py/rpds@v0.20.0...v0.20.1

v0.20.0

Compare Source

What's Changed

• Implements __hash__ for collections by @​FlickerSoul in https://github.com/crate-py/rpds/pull/81

Full Changelog: crate-py/rpds@v0.19.1...v0.20.0

v0.19.1

Compare Source

What's Changed

• Make Python versions in GitHub Actions consistent by @​rominf in https://github.com/crate-py/rpds/pull/80

New Contributors

• @​rominf made their first contribution in [https://github.co

---

Configuration

📅 Schedule: Branch creation - "after 1am and before 3am 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]

⚠ 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 charm-YIu8ppE6-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because pytest-operator (0.35.0) depends on pytest-asyncio (<0.23)
 and no versions of pytest-operator match >0.35.0,<0.36.0, pytest-operator (>=0.35.0,<0.36.0) requires pytest-asyncio (<0.23).
So, because charm depends on both pytest-operator (^0.35.0) and pytest-asyncio (^0.23.6), version solving failed.

[renovate]

⚠️ 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 charm-YIu8ppE6-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

Incompatible constraints in requirements of charm (0.1.0):
ops (>=2.17.1,<2.18.0)
ops (>=2.15.0,<2.16.0)