-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update testing pip deps (minor) #115
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/auto-testing-pip-deps
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 08:55
4e3c2ce
to
836cfe0
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 09:10
836cfe0
to
1d7db2e
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 09:23
1d7db2e
to
3ce6727
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 09:56
3ce6727
to
8ce9e0f
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 13:17
8ce9e0f
to
d4ad1e9
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 19:42
d4ad1e9
to
aeeedab
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 2, 2024 19:56
aeeedab
to
8dda67b
Compare
canonical-iam
approved these changes
Aug 2, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 3, 2024 12:35
8dda67b
to
6b5474b
Compare
canonical-iam
approved these changes
Aug 3, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 3, 2024 15:27
6b5474b
to
18b4762
Compare
canonical-iam
approved these changes
Aug 3, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 3, 2024 23:20
18b4762
to
83e436b
Compare
canonical-iam
previously approved these changes
Aug 3, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 13, 2024 20:13
83e436b
to
c73ea4d
Compare
renovate
bot
changed the title
chore(deps): update dependency pytest-asyncio to v0.23.8
chore(deps): update testing pip deps (minor)
Aug 13, 2024
canonical-iam
approved these changes
Aug 13, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 13, 2024 20:29
c73ea4d
to
088dbde
Compare
canonical-iam
approved these changes
Aug 13, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 13, 2024 20:44
088dbde
to
610c184
Compare
canonical-iam
approved these changes
Aug 13, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 14, 2024 11:57
610c184
to
f08e315
Compare
canonical-iam
approved these changes
Aug 14, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 14, 2024 14:56
f08e315
to
9810932
Compare
canonical-iam
approved these changes
Aug 14, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 15, 2024 13:16
9810932
to
0aaa5ce
Compare
canonical-iam
approved these changes
Aug 15, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 16, 2024 18:26
0aaa5ce
to
f0a95c6
Compare
canonical-iam
previously approved these changes
Aug 16, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 22, 2024 10:49
f0a95c6
to
dc65d7f
Compare
canonical-iam
approved these changes
Aug 22, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 22, 2024 11:23
dc65d7f
to
68ef7bb
Compare
canonical-iam
approved these changes
Aug 22, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 22, 2024 14:50
68ef7bb
to
aa86aaf
Compare
canonical-iam
approved these changes
Aug 22, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 25, 2024 11:30
aa86aaf
to
ba1bdba
Compare
canonical-iam
approved these changes
Aug 25, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 29, 2024 17:11
ba1bdba
to
bef9b61
Compare
canonical-iam
approved these changes
Aug 29, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
August 30, 2024 14:01
bef9b61
to
f1addf9
Compare
canonical-iam
approved these changes
Aug 30, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
September 4, 2024 11:57
f1addf9
to
241a3e7
Compare
canonical-iam
approved these changes
Sep 4, 2024
renovate
bot
force-pushed
the
renovate/auto-testing-pip-deps
branch
from
September 5, 2024 17:31
241a3e7
to
65f910b
Compare
canonical-iam
approved these changes
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
==0.21.2
->==0.24.0
==0.35.0
->==0.36.0
Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.24.0
: pytest-asyncio 0.24.0Compare Source
0.24.0 (2024-08-22)
pytest_asyncio.fixture
. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.@pytest.mark.asyncio
. #812v0.23.8
: pytest-asyncio 0.23.8Compare Source
0.23.8 (2024-07-17)
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.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.post1
: pytest-asyncio 0.23.5.post1Compare 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.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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.