Skip to content

chore(ci): settle PS 5.1 gate TODO as a deliberate scope decision #186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
massive-value merged 1 commit into from
Jul 7, 2026
Merged

chore(ci): settle PS 5.1 gate TODO as a deliberate scope decision #186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading