Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Publish via NuGet.org as a .NET tool

未关闭
#255 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Flash0ver 已经在做这个了。

开始于 2026年2月17日。

评估

这个 Issue 还没有评估数据。

描述

enhancement
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.

Context
主要语言
TypeScript
星标
123
派生
14
平均合并
1 天 2 小时
30 天内合并 PR
70

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getsentry/cli 的其他 Issue

查看 getsentry/cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。