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
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
Over the last week, we've seen @dependabot recreate work less than before
Specifically, in grouped PRs
Scenario:
Have a grouped dependabot PR
with a conflict in package.json/package-lock.json vs main
comment as @dependabot recreate
the rebase logs (for dependabot on github action) show it attempts to create a PR, but there's no change to the PR made - so it stays conflicted
I've noticed this specifically when the group PR wouldn't change what dependency versions it has, but I wanted to recreate to fix up the conflicts.
This is in private repositories, so I don't have direct logs, but definitely seen this happen more and more. Anything you are tracking or have on your end?
Native package manager behavior
No response
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
npm
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
Over the last week, we've seen @dependabot recreate work less than before
Specifically, in grouped PRs
Scenario:
@dependabot recreate
I've noticed this specifically when the group PR wouldn't change what dependency versions it has, but I wanted to recreate to fix up the conflicts.
This is in private repositories, so I don't have direct logs, but definitely seen this happen more and more. Anything you are tracking or have on your end?
Native package manager behavior
No response
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: