What task are you trying to do?
We need to put Windows distribution back on the release schedule. The next release target is 2026-04-22, so the immediate goal is to define and verify the smallest Windows release path that can be shipped responsibly.
What do you do today?
Windows support was previously parked while macOS packaging and release stability took priority. There are older Windows CI flake notes, but there is not yet a current release checklist that confirms the Windows build artifact, signing state, smoke coverage, and publish flow for this release.
What would a good result look like?
PawWork has a documented Windows release path with a concrete build artifact, a decision on signing for this release, a minimal smoke checklist, and clear release notes. If the 2026-04-22 release cannot include a fully signed Windows installer, the issue should record the smallest acceptable fallback and the remaining blocker.
Which audience does this matter to most?
Both
Extra context
This issue intentionally stays separate from macOS Intel support. Windows has different build, signing, and smoke-test risks, so it needs its own tracking issue and acceptance criteria.
What task are you trying to do?
We need to put Windows distribution back on the release schedule. The next release target is 2026-04-22, so the immediate goal is to define and verify the smallest Windows release path that can be shipped responsibly.
What do you do today?
Windows support was previously parked while macOS packaging and release stability took priority. There are older Windows CI flake notes, but there is not yet a current release checklist that confirms the Windows build artifact, signing state, smoke coverage, and publish flow for this release.
What would a good result look like?
PawWork has a documented Windows release path with a concrete build artifact, a decision on signing for this release, a minimal smoke checklist, and clear release notes. If the 2026-04-22 release cannot include a fully signed Windows installer, the issue should record the smallest acceptable fallback and the remaining blocker.
Which audience does this matter to most?
Both
Extra context
This issue intentionally stays separate from macOS Intel support. Windows has different build, signing, and smoke-test risks, so it needs its own tracking issue and acceptance criteria.