-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Grpc.Tools version 2.55.1 not resolved to specific version error #894
Comments
Are you using the current version of cyclonedx-dotnet? I hoped we got rid of that bug. Do you maybe have a different version of grpc.tools referenced directly? |
Currently running the dotnet tool CycloneDX version 3.0.8 , still the same error "Grpc.AspNetCore/2.55.0": { |
With what argument do you call the tool? I want to change the tool to just add all versions of that library in case, but I have no free capacity. A workaround can be, to generate the sboms by refering the "root-component"-projects (meaning your .exe / service-backend ). I recommend doing it that way for increased accuracy anyway and handle all my projects like that. (I generate a frontend and backend bom seperately then) |
dotnet-CycloneDX.exe {projectName}.csproj -o CycloneDXOutputs -fn {projectName}.xml -dpr and it fails sadly on the project that is creating the .exe |
Problem persists even in version 4.0.0 problem is with Grpc.Tools nuget package version range [2.60.0, Dependency (Grpc.Tools) with version range ([2.60.0, )) referenced by (Name:Grpc.AspNetCore Version:2.60.0) did not resolve to a specific version. |
Couple of days ago I started getting this exception when generating SBOM from one of our projects.
Dependency (Grpc.Tools) with version range ([2.55.1, )) referenced by (Name:Grpc.AspNetCore Version:2.55.0) did not resolve to a specific version.
Unable to locate valid bom ref for Grpc.Tools [2.55.1, )
What is the issue here?
The text was updated successfully, but these errors were encountered: