Error
We recently added an RID specific tool to roslyn (roslyn-language-server), but the VMR is publishing this package to the dotnet-tools feed with an incorrect metapackage which is missing every RID except for windows.
Incorrect version from the VMR has this RID config in DotnetToolSettings.xml:
<RuntimeIdentifierPackages>
<RuntimeIdentifierPackage RuntimeIdentifier="win-x64" Id="roslyn-language-server.win-x64"/>
</RuntimeIdentifierPackages>
whereas the roslyn build produces this version with the correct set of RIDs:
<RuntimeIdentifierPackages>
<RuntimeIdentifierPackage RuntimeIdentifier="win-x64" Id="roslyn-language-server.win-x64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="win-arm64" Id="roslyn-language-server.win-arm64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="linux-x64" Id="roslyn-language-server.linux-x64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="linux-arm64" Id="roslyn-language-server.linux-arm64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="linux-musl-x64" Id="roslyn-language-server.linux-musl-x64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="linux-musl-arm64" Id="roslyn-language-server.linux-musl-arm64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="osx-x64" Id="roslyn-language-server.osx-x64"/>
<RuntimeIdentifierPackage RuntimeIdentifier="osx-arm64" Id="roslyn-language-server.osx-arm64"/>
</RuntimeIdentifierPackages>
Links
No response
Root Cause
unknown
Blocking
Affected Releases
Error
We recently added an RID specific tool to roslyn (roslyn-language-server), but the VMR is publishing this package to the dotnet-tools feed with an incorrect metapackage which is missing every RID except for windows.
Incorrect version from the VMR has this RID config in DotnetToolSettings.xml:
whereas the roslyn build produces this version with the correct set of RIDs:
Links
No response
Root Cause
unknown
Blocking
Affected Releases