-
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
Regression: Grouped update includes no details about upgrades #9457
Comments
Grouped update PR for my frontend repo did not have this bug, FYI. (That one is in the GA runner beta, though.) |
We're seeing this too. In the logs I see
|
I've also been experiencing this for a few weeks (npm packages). I have seen this error in the most recent log:
|
@jakecoffman Hi! Just checking you'd seen this issue? It's a pretty serious regression that started almost 2 weeks ago now. |
In #5980 we started handling errors around PR metadata gathering. The idea was the PR change is still good, we shouldn't hold up creating it because we couldn't generate the PR body. As a result of that we lost error reporting to the service, so there may be new bugs around metadata generation that we're not seeing in our error reporting. I think a good first step on this is to start reporting the exception to the service again so we can prioritize and fix them. I'll see if I can round up someone to wire it back up. |
This happened again to me in a public repo (dhensby/readable-tokens#148) Update log
|
Flagging that this is happening for me as well.
What seems to be a side effect, is that I can no longer run the I am assuming the |
Thanks for the examples, we're on it 👍
I wouldn't think that's related, we don't rely on any of the information from the PR body itself, it's purely used for presentation logic. I'll make sure to double check they're not caused by the same underlying problem though. |
I probably didn't fix everyone's issues with #9560 but I think I fixed a common one. For everyone else who experiences this, we should now get a stacktrace in the logs which should make it much easier to track down the problem if you notice it again. Open a new issue in that case if you can! I also opened #9564 to track reporting the errors to the service so we can catch regressions like this in the future. |
@jakecoffman Thank you for the update. Retriggering Dependabot on one of our repos now I see the same issue on the new grouped PR it just created (with the same exception mentioned in #9457 (comment), except now with a stacktrace) - I filed #9565 for this. |
Is there an existing issue for this?
Package ecosystem
Bundler
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
Usually dependabot lists out all the upgraded packages and provides info about the changed versions, but this week, nothing:
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: