Dependabot rebase/update for open group PR closes it #10790
Labels
L: dart:pub
Dart packages via pub
L: github:actions
GitHub Actions
L: python
T: bug 🐞
Something isn't working
Is there an existing issue for this?
Package ecosystem
pip
Package manager version
No response
Language version
Python 3.11
Manifest location and content before the Dependabot update
/requirements.txt
dependabot.yml content
https://github.com/jasonkaedingrhino/dependabot-pip-test/blob/master/.github/dependabot.yml
Updated dependency
Previous:
Open PR updatee:
What you expected to see, versus what you actually saw
The PR was already open. I used
@dependabot rebase
to request a rebase. Then, dependabot closed the PR. No "superseded" message.The dependabot update logs show the problem. It begins checking the
langchain
group but then saysit has already been handled by a previous group
I am aware of other bugs with groups regarding alphabetical order vs array order as specified in the documentation. However, in this case my only other group name
library-patches
is both 2nd in the array order and also 2nd in alphabetical order, meaning that thislangchain
group would seem to always be processed first.There is also a very similar issue open #9845 but that is with Poetry, this uses pip instead. And, also, in that case no PR is created, whereas here the PR is created properly but then later a rebase closes it.
I understand that a "workaround" suggestion might be to try to re-open the PR. However, I want to leave it alone for troubleshooting. I tried to do this with a previous patch version bump, but then dependabot closed the PR immediately again.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue
https://github.com/jasonkaedingrhino/dependabot-pip-test/blob/master/.github/dependabot.yml
This is already the "smallest" version relative to what exists in a private repo. The private repo also points to a private package registry, whereas this one shows the problem even with public PyPI.
The text was updated successfully, but these errors were encountered: