Repository navigation
feat(install): install.ps1 is published beside install.sh, and runs on Windows PowerShell 5.1 - #951
Merged
David-Noble-at-work merged 2 commits intoSep 25, 2026
Conversation
…ndows PowerShell 5.1 Claude-Session: https://claude.ai/code/session_01DuNfZFyfxBoD9pdaiDEMrY
…n Windows PowerShell 5.1 release.yaml's sync step copied install.sh to the site and nothing else, so install.ps1's own usage line -- irm https://devlore.noblefactor.com/install.ps1 | iex -- was a 404. It syncs both scripts now, and the release summary shows the Windows one-liner beside the Unix one. install.ps1 was written for PowerShell 7, which a fresh Windows machine does not have. Ruled 2026-09-24 (#798, ruling 3 reversed): the installer uses what is on the box, Windows PowerShell 5.1, and installs nothing but lore, star and writ. So: #Requires -Version 5.1; Get-OSName reads PSEdition before the $Is* automatic variables, which 5.1 lacks and strict mode would refuse; -UseBasicParsing on every web call, since 5.1's default engages the Internet Explorer parser; TLS 1.2 forced before the first request. The body is otherwise #914's. Verified under pwsh 7 on linux/arm64 against a scratch prefix with a real pre-release. The run under 5.1 on a Windows machine is the owner's, and the plan says so. Resolves #948 Claude-Session: https://claude.ai/code/session_01DuNfZFyfxBoD9pdaiDEMrY
David-Noble-at-work
deleted the
feature/948-install-ps1-is-published-beside
branch
September 25, 2026 04:57
This was referenced Sep 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lane 1 of #949. Design #798: ruling 1 stands; ruling 3 reversed 2026-09-24 (recorded on #798).
release.yaml's sync step copiesinstall.shandinstall.ps1to the site'spublic/, adds both, and the release summary shows the Windows one-liner.irm https://devlore.noblefactor.com/install.ps1 | iexstops being a 404 on the next release.#Requires -Version 5.1;Get-OSNamereadsPSEditionbefore$IsWindows/$IsMacOS/$IsLinux, which 5.1 lacks andSet-StrictModewould refuse;-UseBasicParsingonInvoke-RestMethodandInvoke-WebRequest; TLS 1.2 forced before the first request. One code path, 5.1 and 7, Windows, macOS and Linux. Nothing installed but the products.docs/plans/feature/948-install-ps1-is-published-beside.md,active: the 5.1 live run and the site's publication close after this merges.Resolves #948
Test plan
install.ps1parses under pwsh 7 (0 errors) and every cmdlet, operator and .NET member it uses is inside 5.1's surface (listed in the plan)DEVLORE_TOOLS=writ, pre-releasev0.1.0-dev.20260924074819, checksum verified,writ --version→ buildd54626d2; nothing written outside the prefixrelease.yamlparses as YAML; the sync step's shell block passesbash -n; shellcheck's one finding (SC2164,cd website) is pre-existingcurl -sI https://devlore.noblefactor.com/install.ps1→ 200Time
Computed by the algorithm of noblefactor-ops#188 at merge.