Plan
docs/ROADMAP.md L96-100, Phase 5 — Release & distribution:
Outstanding: editor packaging via winget, and cutting the v2.0 milestone.
The same work appears as row 3 of the priority table at L122 ("Editor packaging and the v2.0 milestone"). Decision 3 at L131 says the editor is "Windows-first, shipped via winget".
What exists today
Schema.Editor builds as an application.
.github/workflows/dotnet.yml installs ktsu.KtsuBuild.Tool, but only uses it for ktsubuild test.
- KtsuBuild already provides
ktsubuild winget generate --version <version>, with project auto-detection (see the KtsuBuild README, winget section).
What's missing
- No step in
dotnet.yml generates or submits winget manifests for the editor. grep -i winget .github/ finds nothing.
- The old
scripts/update-winget-manifests.ps1 no longer exists; only CHANGELOG mentions remain.
- The "What works today" CI/CD bullet at L44-45 claims "winget manifest updates", but nothing implements them. That claim is currently wrong.
Acceptance criteria, from the plan
- A release of Schema produces winget manifests for
Schema.Editor, generated by ktsubuild winget generate or through the shared release pipeline, and submits them.
winget install installs a working editor on Windows.
Out of scope
Cutting the v2.0 milestone is part of the same phase, but it is a release decision rather than code, so it is not part of this issue.
Dependencies
None in this repository. If the org's shared ci.yml pipeline already carries a winget stage, the right move may be to adopt that pipeline rather than add a bespoke step to dotnet.yml.
Plan
docs/ROADMAP.mdL96-100, Phase 5 — Release & distribution:The same work appears as row 3 of the priority table at L122 ("Editor packaging and the v2.0 milestone"). Decision 3 at L131 says the editor is "Windows-first, shipped via winget".
What exists today
Schema.Editorbuilds as an application..github/workflows/dotnet.ymlinstallsktsu.KtsuBuild.Tool, but only uses it forktsubuild test.ktsubuild winget generate --version <version>, with project auto-detection (see the KtsuBuild README,wingetsection).What's missing
dotnet.ymlgenerates or submits winget manifests for the editor.grep -i winget .github/finds nothing.scripts/update-winget-manifests.ps1no longer exists; only CHANGELOG mentions remain.Acceptance criteria, from the plan
Schema.Editor, generated byktsubuild winget generateor through the shared release pipeline, and submits them.winget installinstalls a working editor on Windows.Out of scope
Cutting the v2.0 milestone is part of the same phase, but it is a release decision rather than code, so it is not part of this issue.
Dependencies
None in this repository. If the org's shared
ci.ymlpipeline already carries a winget stage, the right move may be to adopt that pipeline rather than add a bespoke step todotnet.yml.