feat(install): add a winget channel [follow-up, needs signed installer] #409

New issue

Open

opened 2026-08-17 15:44:37 +00:00 by hexajon · 2 comments

hexajon commented

2026-08-17 15:44:37 +00:00

Owner

Add a winget channel for Windows once code-signing is in place. A winget-pkgs submission wants a signed installer. This is a follow-up to the install overhaul. It does NOT block the epic.

Scope

Depends on the code-signing follow-up. Per ADR 0010 (winget deferred).

Acceptance Criteria

winget install madtea works with a signed installer.
The manifest is submitted and maintained.

Depends on: #408

Add a winget channel for Windows once code-signing is in place. A winget-pkgs submission wants a signed installer. This is a follow-up to the install overhaul. It does NOT block the epic. ## Scope Depends on the code-signing follow-up. Per ADR 0010 (winget deferred). ## Acceptance Criteria - [ ] `winget install madtea` works with a signed installer. - [ ] The manifest is submitted and maintained. Depends on: #408

hexajon added the

enhancement

status/blocked

labels

2026-08-17 15:44:37 +00:00

hexajon commented

2026-08-17 15:44:41 +00:00

Author

Owner

Parked behind #408. The dependency is already wired. A winget-pkgs submission needs a signed installer, so nothing here can move until the code-signing certificates exist and #408 ships. This is publish-coupled per ADR 0010 (winget deferred). Nothing to do here until #408 closes.