-
Notifications
You must be signed in to change notification settings - Fork 1k
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
dependabot updater still check poetry explicit
source
#7918
Comments
Thanks for reporting! Yes, it sounds like we could do some extra filtering over Happy to review a PR implementing this! |
Sure, I'll give it a shot, but I don't have much experience with Ruby. |
Note: I've observed that the recent Dependabot update retains the "explicit" source at the beginning, but after this line, Dependabot appears to forget about the explicit setting once more.
|
|
Awesome, thanks so much for persisting on this @lucemia, I will get to your PR as soon as possible! |
Is there an existing issue for this?
Package ecosystem
poetry
Package manager version
poetry 1.6
Language version
python 3.10
Manifest location and content before the Dependabot update
/pyproject.toml
and/poetry.lock
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
Poetry 1.5.0 introduced explicit package source
https://python-poetry.org/docs/repositories/#explicit-package-sources
However, in latest dependabot, the updater will still check package against source marked as
explicit
. Which double the execution time.Native package manager behavior
will not check protobuf against my private pypi
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: