Version 5.2 #16
Unanswered
Pnwcomputers
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
📝 Release Description
🚀 Release v5.2: Menu Fixes, Pipeline Repairs, & Stability Enhancements
This release focuses heavily on squashing runtime bugs, improving CI/CD reliability, and refining code quality to ensure a smoother, crash-free deployment experience.
🐛 Bug Fixes
QuickStart.cmdto use the correct PowerShell parameters (-SkipBloatwareRemoval,-SkipAppInstall,-SkipSystemConfig,-UpdateApps) instead of the non-existent-ConfigFile. All 4 menu choices now execute flawlessly.:startlabel toQuickStart.cmd. Invalid inputs will now loop back to the menu correctly instead of crashingcmd.exe.winget --versionoutputting multiple lines caused the array replacement and[Version]cast to fail. AddedWhere-ObjectandSelect-Object -Last 1to ensure the minimum version check parses robustly.tests/DeployWorkstation.Tests.ps1to correctly check forQuickStart.cmd, resolving a permanent CI failure.upload-artifact@v3to@v4in.github/workflows/test-powershell.yml.🧹 Code Quality & Under-the-Hood
Set-ExecutionPolicyto the top ofDeployWorkstation.ps1(line 26). Previously, if this threw an error mid-file, it could leave the machine in a partially configured state.Get-CimInstance Win32_OperatingSystemcall inExport-HtmlReport. It now correctly reuses the cached$script:OsInfovariable to speed up report generation.$script:IsWin11, which was computed but never referenced in the codebase.🔖 Versioning Consistency
.cmdlauncher) fromv5.1tov5.2to match the repository versioning.Full Changelog: v5.11...v5.2
This discussion was created from the release Version 5.2.
All reactions