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
With the current dependabot.yaml, we check the dependencies with a daily interval. If there is no current open dependabot PR in the repo, dependabot will create 2 PRs as specified in the groups config.
The next time the interval triggers again, we expect Dependabot to take no action (since dependencies has not changed in this case), or update the current PR if there is any changes.
But instead dependabot closes the PR with the following message: "Looks like these dependencies are no longer updatable, so this is no longer needed." This makes no sense to me, since nothing has changed.
Next interval again, since there is no existing PRs, dependabot creates 2 new PRs again. The cycle continues...
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
Use the following yaml. Set the time firstly to a few minutes into the feature to trigger the PR creations. Then update the time again to a few mins into the future, and watch dependabot close the PRs. (Same approach used to show the issue in the image)
Is there an existing issue for this?
Package ecosystem
maven
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
With the current dependabot.yaml, we check the dependencies with a daily interval. If there is no current open dependabot PR in the repo, dependabot will create 2 PRs as specified in the groups config.
The next time the interval triggers again, we expect Dependabot to take no action (since dependencies has not changed in this case), or update the current PR if there is any changes.
But instead dependabot closes the PR with the following message: "Looks like these dependencies are no longer updatable, so this is no longer needed." This makes no sense to me, since nothing has changed.
Next interval again, since there is no existing PRs, dependabot creates 2 new PRs again. The cycle continues...
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
Use the following yaml. Set the time firstly to a few minutes into the feature to trigger the PR creations. Then update the time again to a few mins into the future, and watch dependabot close the PRs. (Same approach used to show the issue in the image)
The text was updated successfully, but these errors were encountered: