Skip to content

Update Python dependencies (8/edge) - #310

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

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

Conversation

@renovate

@renovate renovate Bot commented Apr 21, 2026 •
edited
Loading

Copy link
Copy Markdown

ℹ️ 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
charm-refresh >=3.1.0.2,<4.0.0.0 → >=3.1.1.6,<4.0.0.0 age confidence
charmlibs-rollingops (source, changelog) >=1.0.0,<2.0.0 → >=1.1.1,<2.0.0 age confidence
codespell ^2.2.6 → ^2.4.3 age confidence
coverage ^7.5.0 → ^7.15.4 age confidence
dacite ~=1.9.0 → ~=1.9.2 age confidence
deepmerge >=2.0 → >=2.1.0 age confidence
google-api-core ~=2.17.0 → ~=2.34.0 age confidence
google-cloud-storage (source) ~=2.16.0 → ~=2.19.0 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.2 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.16.3 age confidence

Release Notes

codespell-project/codespell (codespell)

v2.4.3

Compare Source

What's Changed

New Contributors

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

coveragepy/coveragepy (coverage)

v7.15.4

Compare Source

  • Fix: in the HTML report, a source file name containing a double quote (legal
    on POSIX) wasn't escaped where it's dropped into the href of the index
    and prev/next links, so it could close the attribute early and inject markup.
    Page URLs are now escaped. Thanks, Rajath Mohare <pull 2227_>_.

  • Fix: the LCOV report wrote file names and other fields into its
    line-oriented records without neutralizing control characters. A measured
    file whose name contained a newline (legal on POSIX) could forge extra
    records, inflating the coverage seen by tools that read the report. Control
    characters in a field are now replaced. Thanks, Rajath Mohare <pull 2226_>_.

  • Wheels are now provided for Python 3.15.

.. _pull 2226: #​2226
.. _pull 2227: #​2227

.. _changes_7-15-3:

v7.15.3

Compare Source

  • Fix: the sysmon core is incompatible with dynamic contexts. Previously, the
    combination would be prevented when read from the coverage.py configuration.
    But using the context API as pytest-cov does, contexts would be silently
    dropped. Now a warning is issued, thanks to Jisang Han <pull 2234_>.
    Closes issue 2200    .

  • A performance improvement in the low-level line number bookkeeping when
    combining data files, thanks to Kevin Turcios <pull 2239_>_.

  • Performance improvement in HTML reporting by reducing the number of times
    files have to be parsed, thanks to Kevin Turcios <pull 2240_>_.

.. _issue 2200: #​2200
.. _pull 2234: #​2234
.. _pull 2239: #​2239
.. _pull 2240: #​2240

.. _changes_7-15-2:

v7.15.2

Compare Source

  • Fix: one of the performance improvements in 7.15.1 (pull 2215) dramatically
    increased memory use during reporting for large projects. Now we use a
    different approach that is both faster and slimmer than 7.15.0. Fixes issue 2229_.

.. _issue 2229: #​2229

.. _changes_7-15-1:

googleapis/google-cloud-python (google-api-core)

v2.34.0: google-api-core: v2.34.0

Compare Source

Features
Bug Fixes

v2.33.0: google-api-core: v2.33.0

Compare Source

Features
  • api_core: add request-id auto-population logic to gapic_v1 public helpers (#​17738) (68e1313)
  • api-core: add get_universe_domain helper to universe.py (#​17799) (d461da7)
Bug Fixes
  • api-core: prevent overwriting explicit empty strings for optional request_id (#​17798) (07f7503)

v2.32.0: google-api-core: v2.32.0

Compare Source

Features
Bug Fixes
  • api_core: clarify misleading http 404 unimplemented error message (#​17681) (00b9040)

v2.31.0: google-api-core: v2.31.0

Compare Source

Bug Fixes
Documentation

v2.30.3: google-api-core: v2.30.3

Compare Source

Bug Fixes
  • avoid repeated scan of entire venv via packages_distributions() at import time (#​16579) (c5728b24)

v2.30.2: google-api-core: v2.30.2

Compare Source

Bug Fixes

v2.30.1: google-api-core: v2.30.1

Compare Source

v2.30.1 (2026-03-26)

v2.30.0: google-api-core: v2.30.0

Compare Source

Bug Fixes

v2.29.0: google-cloud-secret-manager: v2.29.0

v2.29.0 (2026-06-02)

v2.28.1: google-cloud-firestore: v2.28.1

Bug Fixes

v2.28.0: google-cloud-firestore: v2.28.0

Features
Bug Fixes

v2.27.0: google-cloud-secret-manager: v2.27.0

v2.27.0 (2026-03-26)

v2.26.0: google-cloud-firestore: v2.26.0

Features

v2.25.1: google-cloud-texttospeech: v2.25.1

Bug Fixes
  • [Many APIs] Allow Protobuf 6.x (4757dae)
  • remove setup.cfg configuration for creating universal wheels (#​13659) (59bfd42)

v2.25.0

v2.24.2

v2.24.1

v2.24.0: google-cloud-firestore: v2.24.0

Features

  • use cryptographically secure random for new document ids (#​1162) (3619a31e)

  • expose the variable definition in the Cloud Firestore API (PiperOrigin-RevId: 8775359) (4937235e)

  • Expose the Index.unique parameter (PiperOrigin-RevId: 8654448) (5a17963a)

  • Expose the Database.mongodb_compatible_data_access_mode parameter (PiperOrigin-RevId: 8654448) (5a17963a)

  • Expose the Database.firestore_data_access_mode parameter (PiperOrigin-RevId: 8654448) (5a17963a)

  • Expose the Database.realtime_updates_mode parameter (PiperOrigin-RevId: 8654448) (5a17963a)

Bug Fixes
Documentation
  • Update documentation on several parameters, especially when relating to the new enterprise database edition (PiperOrigin-RevId: 8654448) (5a17963a)

v2.23.0: google-cloud-tasks: v2.23.0

Features

v2.22.0

v2.21.0

v2.20.0

v2.19.2

v2.19.1

v2.19.0

v2.18.0

pre-commit/pre-commit (pre-commit)

v4.6.2

Compare Source

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

Fixes

v4.6.1

Compare Source

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

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 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: p

✂ 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 review from a team, Gu1nness, Mehdi-Bendriss, akram09, patriciareinoso, reneradoi, skourta and smethnani and removed request for a team April 21, 2026 02:56
@renovate

renovate Bot commented Apr 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

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

@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch from 1145bc3 to 3d78e6c Compare April 28, 2026 03:14
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch from 3d78e6c to f75fc92 Compare May 5, 2026 03:33
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from 31a78af to 240af56 Compare May 19, 2026 04:06
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch from 240af56 to f96abbf Compare May 26, 2026 03:24
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from e295344 to 3801c7d Compare June 9, 2026 03:48
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from 56428bf to 8cee7a2 Compare June 23, 2026 04:09
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from 4f872f5 to 2710bb2 Compare July 7, 2026 03:30
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from 172a01a to 9c161e3 Compare July 14, 2026 03:27
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from 3e6daf2 to 86eec18 Compare July 28, 2026 03:23
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch 2 times, most recently from 97d590c to 8b82a75 Compare August 11, 2026 02:49
@renovate
renovate Bot force-pushed the renovate/8/edge-python-dependencies branch from 8b82a75 to 461fdd2 Compare August 18, 2026 04:36
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

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