Publish via NuGet.org as a .NET tool #255
Description
Summary
Publish the Sentry CLI via NuGet.org as a .NET tool.
See also #87.
Remarks
We want to decouple the release of the Sentry CLI for NuGet from the release of the Sentry .NET SDK,
so we can't reuse the name Sentry, which is the "base" .NET SDK.
A lot of tools in the ecosystem prefix their tools with dotnet-, so let's use dotnet-sentry for the ID of the package.
Support .NET SDK 10.0+: The .NET 10 SDK has introduced <DotNetCliTool Version="2"> which also allows platform-specific .NET tools incompatible with .NET SDK 9.0-.
The Sentry CLI is currently released as these self-contained platform-specific executables:
| Release Asset | .NET Runtime Identifier |
|---|---|
| sentry-darwin-arm64 | osx-arm64 |
| sentry-darwin-x64 | osx-x64 |
| sentry-linux-arm64 | linux-arm64 |
| sentry-linux-x64 | linux-x64 |
| sentry-windows-x64.exe | win-x64 |
The "root" package serves as an "entry point" for installing the respective RID-specific tool.
The framework-dependent "any" RID just prints an error that the {Current-Platform} is not supported.
Each RID-specific tool contains the binary of the Sentry-CLI for the respective platform, which is launched by a .NET tool.
These RID-specific tools should be Native-AOT compiled for best startup-performance and lower memory footprints of short-lived processes.