From dbaf0e58b90cf58232c2d02b51926df2458caa99 Mon Sep 17 00:00:00 2001 From: Kadin Bullock Date: Tue, 7 Jul 2026 09:28:17 -0600 Subject: [PATCH] chore(ci): settle PS 5.1 gate TODO as a deliberate scope decision MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The parse-only gate catches the regression class that actually shipped (v0.3.4/v0.4.1). A full frozen updater simulation job is consciously left out — manual frozen-e2e validation covers it and CI maintenance isn't justified until something slips past both. Removes the lingering TODO(Wave 3) so no "someday" marker remains. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/ci.yml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 103d15d..ff5ab32 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -109,10 +109,13 @@ jobs: # from PowerShell 7+ (`pwsh`). This parses both scripts with the real 5.1 # parser and fails on any parse error. # - # TODO(Wave 3): this is a parse-only gate. A fuller frozen old-version -> - # new-version updater simulation job (actually running update.ps1 under - # 5.1 against a fake install tree) is tracked as a follow-up — see - # docs/plans/2026-07-06-full-audit-and-remediation-plan.md §4 item 3. + # Scope: intentionally parse-only. This catches the exact regression class + # that actually shipped (v0.3.4/v0.4.1 were PS 5.1 parse/exec failures). A + # full frozen old->new updater simulation under 5.1 (build a bundle + fake + # install tree, run update.ps1, assert the version flip) is deliberately NOT + # automated here: the release's manual frozen-e2e validation covers it, and + # the CI cost/maintenance isn't justified unless an updater regression ever + # slips past both this gate and that manual check. ps51-parse-gate: runs-on: windows-latest