chore(deps): update dependency pytest-asyncio to ^0.25.0

[ibm-mend-app]

This PR contains the following updates:

Package	Type	Update	Change
pytest-asyncio (changelog)	dev-dependencies	minor	^0.23.0 -> ^0.25.0

---

Release Notes

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

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

[ibm-mend-app]

⚠️ 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 skillsnetwork-nDNUhJi3-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's supported Python range (>=3.8,<4.0) is not compatible with some of the required packages Python requirement:
  - pytest-asyncio requires Python >=3.9, so it will not be satisfied for Python >=3.8,<3.9

Because no versions of pytest-asyncio match >0.25.0,<0.26.0
 and pytest-asyncio (0.25.0) requires Python >=3.9, pytest-asyncio is forbidden.
So, because skillsnetwork depends on pytest-asyncio (^0.25.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.9,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers