Nuget UpdateArtifacts fails if global.json is present #32654
Replies: 2 comments
-
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. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
it seems we should start extract dotnet version from an optional |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
A Mend.io-hosted app
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
I'm running a dotnet repo with a global.json and configured to generate locks file via
global.json specify .net8 (v 8.0.404) but Renovate Bot proceeds to install net9.0 and then try executing
dotnet new
in the working folder. That fails, correctly, as runningdotnet new
respects the local global.json.Assumption is that resolution requires either to run the
dotnet new
in another folder or installing the sdk version configured in the global.json.I cannot change the global.json, is there a way to instruct Renovate to use net8 via renovate.json?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions