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
{{ message }}
This repository was archived by the owner on Apr 27, 2026. It is now read-only.
Describe the bug
The 3rd-party tool dotnet-format recently published an update (5.1.250801). After this update, all of my dotnet lint targets started failing with the following error
Cannot add package. Manifest file already contains version 5.1.225507 of the package dotnet-format. Uninstall/install or edit manifest file C:\Users\bcallaghan\Source\Repos\etogy-workspace\.config\dotnet-tools.json to specify the new version 5.1.250801.
To Reproduce
Specify an older version of dotnet-format in the dotnet-tools.json manifest file (e.g. 5.1.225507)
Run the lint target of a dotnet project (e.g. nx lint my-dotnet-proj)
Expected behavior
The executor should properly handle out-of-date versions so that the lint target can still run.
Environment:
OS: Windows
Version: 0.11.0
Additional context
The error is directly caused by the redundant tool install before running dotnet-format. One possible strategy for handling out-of-date versions is to update to the latest version each time. Another possible strategy is to lock-in to a specific version (as Nx does with Angular) and avoid re-installing the tool after that.
Describe the bug
The 3rd-party tool dotnet-format recently published an update (5.1.250801). After this update, all of my dotnet lint targets started failing with the following error
To Reproduce
dotnet-tools.jsonmanifest file (e.g. 5.1.225507)nx lint my-dotnet-proj)Expected behavior
The executor should properly handle out-of-date versions so that the lint target can still run.
Environment:
Additional context
The error is directly caused by the redundant tool install before running dotnet-format. One possible strategy for handling out-of-date versions is to update to the latest version each time. Another possible strategy is to lock-in to a specific version (as Nx does with Angular) and avoid re-installing the tool after that.