Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.5.0
->3.7.1
^0.21.2
->^0.23.0
Release Notes
pre-commit/pre-commit (pre-commit)
v3.7.1
Compare Source
==================
Fixes
language: rust
default language version check whenrust-toolchain.toml
is present.
v3.7.0
Compare Source
==================
Features
docker
anddocker_image
hooks when--color
is specified.Fixes
fail_fast
for individual hooks stopping when previous hooks had failed.Updating
fail_fast
was fixed. If you want the pre-3.7.0behaviour, add
fail_fast: true
to all hooks before the lastfail_fast
hook.
v3.6.2
Compare Source
==================
Fixes
git commit --all
.v3.6.1
Compare Source
==================
Fixes
PYTHONEXECUTABLE
from environment when running.v3.6.0
Compare Source
==================
Features
minimum_pre_commit_version
first when parsing configs.Fixes
importlib.resources
.Updating
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.23.7
: pytest-asyncio 0.23.7Compare Source
0.23.7 (2024-05-19)
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.6Compare Source
0.23.6 (2024-03-19)
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.5Compare Source
0.23.5 (2024-02-09)
asyncio.get_event_loop()
from affecting test cases #757Known 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.4Compare Source
0.23.4 (2024-01-28)
v0.23.3
: pytest-asyncio 0.23.3Compare Source
0.23.3 (2024-01-01)
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.2Compare Source
0.23.2 (2023-12-04)
v0.23.1
: pytest-asyncio 0.23.1Compare Source
0.23.1 (2023-12-03)
v0.23.0
: pytest-asyncio 0.23.0Compare Source
This release is backwards-compatible with v0.21. Changes are
non-breaking, unless you upgrade from v0.22.
loops with class, module, package, and session scopes can be
requested via the scope keyword argument to the asyncio
mark.
non-default or multiple event loops #662
pytest_asyncio.is_async_test
which returns whether atest item is managed by pytest-asyncio #376
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)
via the asyncio_event_loop mark. #620
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.
Configuration
📅 Schedule: Branch creation - "after 8am on saturday" in timezone Australia/Brisbane, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.