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
Describtion
When installing the new version an Azure.Identity 1.10.4 moderate severity vulnerability is preventing you from running it. When trying to update that library to the latest, the application throws an NSwag error.
To Reproduce
Steps to reproduce the behaviour:
dotnet new install Clean.Architecture.Solution.Template::8.0.5
dotnet new ca-sln --client-framework Angular --output test (or React one)
cd test/src/Web -> dotnet run
see error
if you disable warnings as errors you get another error, see attached log.txt
-- Alternatively --
dotnet new install Clean.Architecture.Solution.Template::8.0.5
dotnet new ca-sln --client-framework Angular --output test (or React one)
update the Azure.Identity 1.10.4 to the latest
try to run again
see error
Expected behaviour
The code to either support the latest version with no vulnerability or clarification on if the warning as error should be bypassed despite the vulnerability
The text was updated successfully, but these errors were encountered:
Change version of Azure.Identity in Directory.Packages.props file from 1.10.4 to 1.11.0 solve this problem
More information in GitHub Advisory Database
Change version of Azure.Identity in Directory.Packages.props file from 1.10.4 to 1.11.0 solve this problem More information in GitHub Advisory Database
That did not work and I still get the same error as seen in the log file I uploaded
Describtion
When installing the new version an Azure.Identity 1.10.4 moderate severity vulnerability is preventing you from running it. When trying to update that library to the latest, the application throws an NSwag error.
To Reproduce
Steps to reproduce the behaviour:
if you disable warnings as errors you get another error, see attached
log.txt
-- Alternatively --
Expected behaviour
The code to either support the latest version with no vulnerability or clarification on if the warning as error should be bypassed despite the vulnerability
The text was updated successfully, but these errors were encountered: