docs(install): add a winget install path for Windows

未关闭 适合新手
#2,208 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1-3 小时
新手友好度
76/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown, typescript
领域
documentation

调研方向

阅读 docs-lab/start/installation.md,尤其是 Package managers、Updating 和 Uninstalling 部分,并检查链接的 microsoft/winget-pkgs#461616 中 winget 清单的状态。确认软件包标识符且清单获批后,添加安装、升级和卸载命令,并注明 winget 会在不需要 Node.js 的情况下安装独立二进制文件;当三个命令和该说明都出现在相关部分时,即为完成。

由索引模型根据 Issue 内容生成。

描述

Where

https://openspec.dev/docs/installation (docs-lab/start/installation.md), the "Package managers" section: Homebrew, Yarn, Bun, Deno, Nix.

What is wrong or missing

There is no Windows package-manager path. Since 1.15.0 the Windows standalone binary makes one possible without Node.js, and it is already staged in the Windows Package Manager community repo, so this is now only a docs gap:

  • microsoft/winget-pkgs#461616 — FissionAI.OpenSpec 1.15.0, InstallerType: portable, Commands: openspec, x64 and arm64, version-pinned release URLs, hashes from the release's SHA256SUMS. Validation is complete; it is waiting on a winget-pkgs moderator to approve and merge.
  • Nothing is needed from this repo. The manifest is metadata only: winget copies the release .exe, creates the openspec shim and writes the ARP entry itself.
  • I am not the publisher. I opened the manifest because I use OpenSpec on Windows and wanted it available there. I am happy to keep bumping it release by release, or to hand it over / wire it into your release workflow (vedantmgoyal9/winget-releaser) if you would rather own the channel.

For reference, the same thing happened with Homebrew in #333: the packaging work is done outside this repo, and this repo only needs to mention it once it exists.

What it should say instead

A ### winget entry under "Package managers", in the shape the Homebrew entry already uses:

winget install FissionAI.OpenSpec

plus the pair from "Updating" / "Uninstalling" (winget upgrade FissionAI.OpenSpec, winget uninstall FissionAI.OpenSpec) and one line saying it installs the standalone binary, so Node.js is not involved.

One question before that section is written: is FissionAI.OpenSpec the identifier you want? The convention is Publisher.Package from the repo owner and app name, and hyphens are not allowed in the identifier, so Fission-AI becomes FissionAI. It is permanent once published — winget cannot rename a package — so a rename later would mean publishing under a second id and abandoning the first. If you would prefer a different id, say so and I will redo the manifest before it publishes. I asked the same question in #1989 on 2026-10-25; this issue is the focused version of it, since that thread is about self-update and the standalone build rather than install channels.


Drafted with an AI assistant (Pi), reviewed and posted by me.

主要语言
TypeScript
星标
74.9k
派生
5.1k
平均合并
2 天 10 小时
30 天内合并 PR
53

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

Fission-AI/OpenSpec 的其他 Issue

查看 Fission-AI/OpenSpec 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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