Skip to content

Update Python dependencies (6/edge)#300

Open
renovate[bot] wants to merge 1 commit into
6/edgefrom
renovate/6/edge-python-dependencies
Open

Update Python dependencies (6/edge)#300
renovate[bot] wants to merge 1 commit into
6/edgefrom
renovate/6/edge-python-dependencies

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Apr 21, 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.16.0 age confidence
allure-pytest-default-results ^0.1.2 → ^0.1.4 age confidence
codespell ^2.2.6 → ^2.4.2 age confidence
coverage ^7.5.0 → ^7.14.1 age confidence
dacite ~=1.9.0 → ~=1.9.2 age confidence
mongomock (changelog) ^4.2.0.post1 → ^4.3.0 age confidence
poetry-core >=2.0 → >=2.4.1 age confidence
pre-commit ^4.0.1 → ^4.6.0 age confidence
pytest-asyncio (changelog) ^0.21.1 → ^0.26.0 age confidence
pytest-operator ^0.36.0 → ^0.43.2 age confidence
pyyaml (source) ~=6.0.2 → ~=6.0.3 age confidence
ruff (source, changelog) ^0.7.2 → ^0.15.15 age confidence

Release Notes

allure-framework/allure-python (allure-pytest)

v2.16.0

Compare Source

🚀 New Features

👻 Internal Changes

👀 Links

Commits since 2.15.3

canonical/allure-pytest-default-results (allure-pytest-default-results)

v0.1.4

Compare Source

What's Changed
New Contributors

Full Changelog: canonical/allure-pytest-default-results@v0.1.3...v0.1.4

codespell-project/codespell (codespell)

v2.4.2

Compare Source

Highlights

  • Fixed compatibility with chardet 7+

What's Changed

New Contributors

Full Changelog: codespell-project/codespell@v2.4.1...v2.4.2

coveragepy/coveragepy (coverage)

v7.14.1

Compare Source

  • Fix: the HTML report used typographic niceties to make file paths more
    readable by adding a small amount of space around slashes. Those spaces
    interfered with searching the page for file paths of interest. Now the report
    uses CSS to accomplish the same visual tweak so that searches with slashes
    work correctly. Closes issue 2170_.

  • Add a 3.16 PyPI classifier <hugo-316_>_ since we test on the 3.16 main
    branch.

.. _issue 2170: #​2170
.. _hugo-316: https://mastodon.social/@​hugovk/116588523571204490

.. _changes_7-14-0:

v7.14.0

Compare Source

  • Feature: now when running one of the reporting commands, if there are
    parallel data files that need combining, they will be implicitly combined
    before creating the report. There is no option to avoid the combination; let
    us know if you have a use case that requires it. Thanks, Tim Hatch <pull 2162_>. Closes issue 1781.

  • Fix: the output from combine was too verbose, listing each file
    considered. Now it shows a single line with the counts of files combined,
    files skipped, and files with errors. The -q flag suppresses this line.
    The old detailed lines are available with the new --debug=combine option.

  • Fix: running a Python file through a symlink now sets the sys.path correctly,
    matching regular Python behavior. Fixes issue 2157_.

  • Fix: Collector.flush_data could fail with "RuntimeError: Set changed
    size during iteration" when a tracer in another thread added a line to the
    per-file set that add_lines (or add_arcs) was iterating. The values
    passed to CoverageData are now snapshotted via dict.copy() and
    set.copy(), which are atomic under the GIL. Thanks, Alex Vandiver <pull 2165_>_.

  • Fix: the soft keyword lazy is now bolded in HTML reports.

  • We are no longer testing eventlet support. Eventlet started issuing stern
    deprecation warnings that break our tests. Our support code is still there.

.. _issue 1781: #​1781
.. _issue 2157: #​2157
.. _pull 2162: #​2162
.. _pull 2165: #​2165

.. _changes_7-13-5:

v7.13.5

Compare Source

  • Fix: issue 2138_ describes a memory leak that happened when repeatedly
    using the Coverage API with in-memory data. This is now fixed.

  • Fix: the markdown-formatted coverage report didn't fully escape special
    characters in file paths (issue 2141). This would be very unlikely to
    cause a problem, but now it's done properly, thanks to Ellie Ayla <pull 2142_>    .

  • Fix: the C extension wouldn't build on VS2019, but now it does (issue 2145_).

.. _issue 2138: #​2138
.. _issue 2141: #​2141
.. _pull 2142: #​2142
.. _issue 2145: #​2145

.. _changes_7-13-4:

v7.13.4

Compare Source

  • Fix: the third-party code fix in 7.13.3 required examining the parent
    directories where coverage was run. In the unusual situation that one of the
    parent directories is unreadable, a PermissionError would occur, as
    described in issue 2129_. This is now fixed.

  • Fix: in test suites that change sys.path, coverage.py could fail with
    "RuntimeError: Set changed size during iteration" as described and fixed in
    pull 2130_. Thanks, Noah Fatsi.

  • We now publish ppc64le wheels, thanks to Pankhudi Jain <pull 2121_>_.

.. _pull 2121: #​2121
.. _issue 2129: #​2129
.. _pull 2130: #​2130

.. _changes_7-13-3:

v7.13.3

Compare Source

  • Fix: in some situations, third-party code was measured when it shouldn't have
    been, slowing down test execution. This happened with layered virtual
    environments such as uv sometimes makes. The problem is fixed, closing issue 2082_. Now any directory on sys.path that is inside a virtualenv is
    considered third-party code.

.. _issue 2082: #​2082

.. _changes_7-13-2:

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

v2.4.1

Compare Source

Fixed
  • Fix an issue where certain marker operations (mostly used with extra markers) resulted in wrong markers (#​943).

v2.4.0

Compare Source

Changed
  • Update list of supported licenses (#​935).
Vendoring

v2.3.2

Compare Source

Changed
  • Update list of supported licenses (#​917).
Fixed
  • Fix an issue where platform_release could not be parsed on Debian Trixie (#​930).
  • Fix an issue where using project.readme.text in the pyproject.toml file resulted in broken metadata (#​914).
  • Fix an issue where dependency groups were considered equal when their resolved dependencies were equal, even if the groups themselves were not (#​919).
  • Fix an issue where removing a dependency from a group that included another group resulted in other dependencies being added to the included group (#​922).
  • Fix an issue where PEP 735 include-group entries were lost when [tool.poetry.group] also defined include-groups for the same group (#​924).
  • Fix an issue where the union of <value> not in <marker> constraints was wrongly treated as always satisfied (#​925).
  • Fix an issue where a post release with a local version identifier was wrongly allowed by a > version constraint (#​921).
  • Fix an issue where a version with the local version identifier 0 was treated as equal to the corresponding public version (#​920).
  • Fix an issue where a != <version> constraint wrongly disallowed pre releases and post releases of the specified version (#​929).
  • Fix an issue where in and not in constraints were wrongly not allowed by specific compound constraints (#​927).
  • Fix an issue where data entries in generated setup.py files were duplicated (#​923).
pre-commit/pre-commit (pre-commit)

v4.6.0

Compare Source

==================

Features
  • pre-commit hook-impl: allow --hook-dir to be missing to enable easier
    usage with git 2.54+ git hooks.
Fixes
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 w

✂ Note

PR body was truncated to here.

@renovate renovate Bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Apr 21, 2026
@renovate renovate Bot requested a review from a team April 21, 2026 02:53
@renovate renovate Bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Apr 21, 2026
@renovate renovate Bot requested review from Gu1nness, Mehdi-Bendriss, akram09, patriciareinoso, reneradoi, skourta and smethnani and removed request for a team April 21, 2026 02:53
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Apr 21, 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...

Creating virtualenv mongo-charms-single-kernel-PO-Mbn2F-py3.14 in /home/ubuntu/.cache/pypoetry/virtualenvs

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

@github-actions github-actions Bot added the Libraries: Out of sync The charm libs used are out-of-sync label Apr 21, 2026
@renovate renovate Bot force-pushed the renovate/6/edge-python-dependencies branch 2 times, most recently from 4a56d07 to 424b552 Compare May 5, 2026 02:56
@renovate renovate Bot force-pushed the renovate/6/edge-python-dependencies branch 2 times, most recently from afddd27 to 869b59a Compare May 19, 2026 04:04
@renovate renovate Bot force-pushed the renovate/6/edge-python-dependencies branch from 869b59a to dc04d04 Compare May 26, 2026 03:23
@renovate renovate Bot force-pushed the renovate/6/edge-python-dependencies branch from dc04d04 to a8907a2 Compare June 2, 2026 04:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@patriciareinoso patriciareinoso Awaiting requested review from patriciareinoso patriciareinoso was automatically assigned from canonical/data-nosql

@Gu1nness Gu1nness Awaiting requested review from Gu1nness Gu1nness was automatically assigned from canonical/data-nosql

@akram09 akram09 Awaiting requested review from akram09 akram09 was automatically assigned from canonical/data-nosql

@skourta skourta Awaiting requested review from skourta skourta was automatically assigned from canonical/data-nosql

@Mehdi-Bendriss Mehdi-Bendriss Awaiting requested review from Mehdi-Bendriss Mehdi-Bendriss was automatically assigned from canonical/data-nosql

@smethnani smethnani Awaiting requested review from smethnani smethnani was automatically assigned from canonical/data-nosql

@reneradoi reneradoi Awaiting requested review from reneradoi reneradoi was automatically assigned from canonical/data-nosql

At least 2 approving reviews are required to merge this pull request.

Assignees

No one assigned

Labels

Libraries: Out of sync The charm libs used are out-of-sync 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