Skip to content

⬆ update pytest-asyncio requirement from ~=1.3.0 to >=1.3,<1.5 #306

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
Closed

⬆ update pytest-asyncio requirement from ~=1.3.0 to >=1.3,<1.5 #306

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ members = [
[dependency-groups]
dev = [
"pytest~=9.0",
"pytest-asyncio~=1.3.0",
"pytest-asyncio>=1.3,<1.5",

@chatgpt-codex-connector chatgpt-codex-connector Bot May 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the lockfile with the new pytest-asyncio constraint

Changing only pyproject.toml leaves uv.lock still recording pytest-asyncio with specifier ~=1.3.0 and the locked package at version 1.3.0, so lockfile-based installs do not actually exercise the newly permitted 1.4.x release. I checked uv sync --help; --locked asserts the lockfile remains unchanged and --frozen syncs without updating it, so those workflows will keep using/requiring the stale lock instead of this dependency update. Please regenerate and commit uv.lock alongside this constraint change.

Useful? React with 👍 / 👎.

"pytest-mock~=3.15",
"coverage~=7.6",
"ruff~=0.15.10",
Expand Down
Loading