You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you expected to see, versus what you actually saw
Up until recently (perhaps when I've added enable-beta-ecosystems: true, not sure) I was getting pull requests with all three files below being updated.
All of following files were upgraded accordingly:
pyproject.toml
src/requirements-dev.txt
src/requirements.txt
Current behaviour/issue:
At the moment only pyproject.toml gets updated. No updates to src/requirements* files.
Native package manager behavior
Requirements files were generated with uv pip compile, but no mention of uv was required in dependabot configuration.
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Package ecosystem
pip
Package manager version
No response
Language version
requires-python = '>=3.12'
Manifest location and content before the Dependabot update
dependabot.yml content
Amongst others.
Please note that I am also affected by #11352, unsure if related.
Updated dependency
psycopg[binary] from 3.2.4 to 3.2.5:
in
pyproject.toml
.What you expected to see, versus what you actually saw
Up until recently (perhaps when I've added
enable-beta-ecosystems: true
, not sure) I was getting pull requests with all three files below being updated.All of following files were upgraded accordingly:
pyproject.toml
src/requirements-dev.txt
src/requirements.txt
Current behaviour/issue:
At the moment only
pyproject.toml
gets updated. No updates tosrc/requirements*
files.Native package manager behavior
Requirements files were generated with
uv pip compile
, but no mention ofuv
was required in dependabot configuration.Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: