Artifact Update Problem - NuGet PackageSourceMapping #29436
Replies: 2 comments 2 replies
-
The error is thrown from nuget itself and not directly by Renovate. I suggest searching for the term "PackageSourceMapping is enabled and there are multiple package sources associated with the same key(s)" to work out why it's an error and then we might be able to work out if there's anything different which Renovate can do to avoid it |
Beta Was this translation helpful? Give feedback.
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. To get started, please read our guide on creating a minimal reproduction. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
We have many repositories that successfully use Renovate with NuGet Package Source Mapping without lock files. However, our one repository that uses lock files is having issues updating them. Every new pull request ends up with an "Artifact Update Problem" comment from Renovate with the error:
We have the same
NuGet.Config
in every repository (including the one that fails):We don't have a
nuget
section defined inrenovate.json
.I don't see a problem with our configuration, so I suspect this is an issue with Renovate when dealing with NuGet lock files.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions