-
Notifications
You must be signed in to change notification settings - Fork 1.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
Problem with grouping updates #10287
Comments
@jakecoffman Could I get your help in triaging this? I don't see anything that's specific to the NuGet updater (i.e., it doesn't do anything specific with groups that I know of. Have you seen similar issues with other ecosystems? |
This might be unrelated, but the stacktrace exactly matches issues recently reported here:
L285: "Error while generating commit message: Passed dependabot-core/common/lib/dependabot/pull_request_creator/message_builder.rb Lines 284 to 288 in 8441dba
The issue in tinglesoftware/dependabot-azure-devops#1232 was ultimately caused due to auth issues accessing the private nuget-feed, which is a known issue with dependabot-core when consuming Azure DevOps NuGet feeds (see: #8927). However there are no auth errors are mentioned in OP's logs, so the root cause may be different here but the output from NuGetUpdater.Cli appears to be the same; no files were changed. The comment #9555 (comment) also suggest this might be a NuGet auth issue |
Have you seen similar issues with other no |
https://github.com/tinglesoftware/dependabot-azure-devops/issues/1257 using this docker image and |
@Maggus85 or @brettfo are you able to close this issue? It is not an issue with dependabot-core, it is an auth issue in https://github.com/tinglesoftware/dependabot-azure-devops |
Is there an existing issue for this?
Package ecosystem
Nuget
Package manager version
No response
Language version
C#
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
I wanted to create one pr that updates the packages from our internal feed and a second that updates the others nugets.
For this reason, I added a section
Without this section, everything works, but a lot of pr is created, which is not the expected behavior
Translated with DeepL.com (free version)
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
No response
The text was updated successfully, but these errors were encountered: