Repository navigation
build(deps): bump pytest-asyncio from 0.21.2 to 1.3.0 - #597
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #597 +/- ##
=======================================
Coverage 90.12% 90.12%
=======================================
Files 55 55
Lines 2512 2512
=======================================
Hits 2264 2264
Misses 248 248 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
MateoLostanlen
force-pushed
the
dependabot/uv/main/pytest-asyncio-1.3.0
branch
from
May 15, 2026 11:24
9e87261 to
f1915bf
Compare
MateoLostanlen
force-pushed
the
dependabot/uv/main/pytest-asyncio-1.3.0
branch
2 times, most recently
from
May 15, 2026 12:10
59f4e0a to
33d4f10
Compare
Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) from 0.21.2 to 1.3.0. - [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases) - [Commits](pytest-dev/pytest-asyncio@v0.21.2...v1.3.0) --- updated-dependencies: - dependency-name: pytest-asyncio dependency-version: 1.3.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
pytest-asyncio 1.0 removed support for the session-scoped 'event_loop' fixture that this repo defined in src/tests/conftest.py. With that fixture gone, function-scoped async fixtures get a fresh event loop per test, while the module-level SQLAlchemy async engine is bound to whichever loop imported it — so asyncpg raises 'Future attached to a different loop' the moment a fixture tries to use the engine. Migration: - Drop the custom 'event_loop' fixture entirely; pytest-asyncio 1.x manages the loop itself. - Add asyncio_default_fixture_loop_scope = 'session' and asyncio_default_test_loop_scope = 'session' under [tool.pytest.ini_options] so all async fixtures and tests share one loop for the whole session — same behaviour as the old custom fixture, just expressed through the supported config knobs. - Add an explicit loop_scope='session' on every @pytest_asyncio.fixture for belt-and-braces (in case fixture defaults aren't applied to decorators with explicit scope=). Also pin the pyro-camera-api-client git dep via [tool.uv.sources] so 'uv sync --locked' doesn't re-resolve the moving 'main' branch during Docker build.
MateoLostanlen
force-pushed
the
dependabot/uv/main/pytest-asyncio-1.3.0
branch
from
May 15, 2026 12:15
33d4f10 to
015bcb8
Compare
MateoLostanlen
approved these changes
May 15, 2026
MateoLostanlen
left a comment
Member
There was a problem hiding this comment.
Approving — pytest-asyncio 1.x migration done: src/pytest.ini sets asyncio_default_*_loop_scope=session (read inside the container thanks to the ./src/:/app/ mount), custom event_loop fixture dropped, and every @pytest_asyncio.fixture decorator carries loop_scope='session' belt-and-braces. 481 backend tests pass. CI 23/23 green.
This file contains hidden or 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
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.
Bumps pytest-asyncio from 0.21.2 to 1.3.0.
Release notes
Sourced from pytest-asyncio's releases.
... (truncated)
Commits
2e9695fdocs: Compile changelog for v1.3.0dd0e9badocs: Reference correct issue in news fragment.4c31abeBuild(deps): Bump nh3 from 0.3.1 to 0.3.213e9477Link to migration guides from changelog4d2cf3ctests: handle Python 3.14 DefaultEventLoopPolicy deprecation warningsee3549btest: Remove obsolete test for the event_loop fixture.7a67c82tests: Fix failing test by preventing warning conversion to error.a17b689test: add pytest config to isolated test directories18afc9dfix(tests): replace runpytest_subprocess with runpytestcdc6bd1Add support for pytest 9 and drop Python 3.9 supportDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)