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
I expected a PR to be raised for the 'minor' group however no pull request was created, output from depenabot logs:
+------------------------------------------------------------------------------------------------------------------------------------+
| Changes to Dependabot Pull Requests |
+---------+--------------------------------------------------------------------------------------------------------------------------+
| created | cssbundling-rails ( from 1.4.1 to 1.4.2 ), slack-ruby-block-kit ( from 0.25.0 to 0.26.0 ), turbo-rails ( from 2.0.11 ... |
+---------+--------------------------------------------------------------------------------------------------------------------------+
Error message on the dependabot update detail screen:
Dependabot failed to create a pull request
Dependabot ran into an issue when attempting to create the pull request
Dependabot encountered the following error:
POST https://api.github.com/repos/korukids/response/git/trees: 422 - Must supply a valid tree.mode // See: https://docs.github.com/rest/git/trees#create-a-tree
[Troubleshoot Dependabot errors](https://docs.github.com/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)
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:
Hey @NGMarmaduke@gs-karolbajko, I'm currently investigating this issue. It appears to only be affecting the bundler, and I'm still working to identify the root cause. The problem seems to have emerged when we released gem version 0.299.0 for dependabot. I'll keep you updated on any findings.
Is there an existing issue for this?
Package ecosystem
Bundler
Package manager version
No response
Language version
Ruby 3.4.1
Manifest location and content before the Dependabot update
/Gemfile
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
I expected a PR to be raised for the 'minor' group however no pull request was created, output from depenabot logs:
Error message on the dependabot update detail screen:
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: