Skip to content

Commit 7c5789b

Browse files
authored
Merge pull request #32 from fadwen/release/v0.30.0
release: 0.30.0
2 parents 26229c9 + 19c6e93 commit 7c5789b

2 files changed

Lines changed: 22 additions & 16 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,15 @@ release notes.
1111

1212
## [Unreleased]
1313

14+
Nothing yet.
15+
16+
## [0.30.0] - 2026-10-08
17+
18+
Three Win32 harness changes, found by running a blog post's demo on a developer machine and on the lab
19+
device: the launcher no longer passes a per-user `cmd.exe` setting on to the install command, the 32-bit
20+
host warning reads the batch file an install command names, and `-Architecture` follows the device's own
21+
64-bit host, so the Win32 commands run unchanged on Windows on ARM.
22+
1423
### Changed
1524

1625
- `Invoke-IntuneDetectionTest`, `Invoke-IntuneRequirementTest` and `Invoke-IntuneWin32AppTest` no
@@ -51,6 +60,7 @@ The harness, a rule, the evidence and the help follow the device now.
5160
error text attached, no post-detection. The harness now reports Failed, skips the post-detection and warns
5261
that the exit code was 0. A detection that writes to stderr and exits 0 is still Without issues, as before.
5362
Measured in user context on the lab device with five one-off remediations (round 11, `REM-STDERR-*`).
63+
5464
## [0.28.0] - 2026-10-06
5565

5666
Two commands run several times faster, the fixer applies eight more edits, the Graph calls are retried
@@ -582,7 +592,8 @@ Nothing any command does has changed.
582592

583593
- Static rules: `Test-IntuneScript`.
584594

585-
[Unreleased]: https://github.com/fadwen/IntuneScriptLab/compare/v0.29.0...HEAD
595+
[Unreleased]: https://github.com/fadwen/IntuneScriptLab/compare/v0.30.0...HEAD
596+
[0.30.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.29.0...v0.30.0
586597
[0.29.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.28.0...v0.29.0
587598
[0.28.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.27.0...v0.28.0
588599
[0.27.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.26.0...v0.27.0

‎IntuneScriptLab.psd1‎

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
@{
22
# Module manifest for IntuneScriptLab
33
RootModule = 'IntuneScriptLab.psm1'
4-
ModuleVersion = '0.29.0'
4+
ModuleVersion = '0.30.0'
55
GUID = '3f6b2c9e-7d41-4a8f-9c2b-5e0d8a1f4b76'
66
Author = 'Jeffrey Stuhr'
77
CompanyName = ''
@@ -64,6 +64,14 @@ pre-flight over the tenant's deployed scripts and readers for the agent's logs
6464
LicenseUri = 'https://github.com/fadwen/IntuneScriptLab/blob/main/LICENSE'
6565
ProjectUri = 'https://github.com/fadwen/IntuneScriptLab'
6666
ReleaseNotes = @'
67+
0.30.0 - Invoke-IntuneDetectionTest, Invoke-IntuneRequirementTest and Invoke-IntuneWin32AppTest no
68+
longer default -Architecture to x64, which Windows on ARM refuses; left out, it is the
69+
device's 64-bit host (x64, or arm64 on ARM), the one the agent uses. Two Win32 fixes: the
70+
launcher starts its child without NoDefaultCurrentDirectoryInExePath, a per-user cmd.exe
71+
setting that made a bare install.cmd fail with "not recognized" although the agent's
72+
cmd.exe finds it; and the 32-bit host warning also reads the batch file an install or
73+
uninstall command names, where a powershell.exe call runs 32-bit just the same. See
74+
CHANGELOG.md.
6775
0.29.0 - A remediation that writes to stderr is a script error on the device whatever its exit code:
6876
RemediationStatus 3, Graph scriptError, the error text attached, no post-detection.
6977
Invoke-IntuneRemediationTest reported Recurred for that run since round 1; it reports Failed,
@@ -84,20 +92,7 @@ pre-flight over the tenant's deployed scripts and readers for the agent's logs
8492
Invoke-IntuneRequirementTest take script paths from the pipeline; every result type has a
8593
format view. The in-box module table is held against the host's Windows PowerShell by a
8694
test, as the PowerShell 7-only tables are. See CHANGELOG.md.
87-
0.27.0 - Harness: a user-context run started from PowerShell 7 gave the 5.1 host PowerShell 7's
88-
module path (no Cert: drive, Security cmdlets failing to load); -Credential did not find
89-
a Microsoft Entra account's session, because Windows names such an account after its
90-
display name and not its sign-in name; a refused folder grant lost its message under
91-
-ErrorAction Stop on 5.1. Rules, from a tenth validation round: IslPowerShell7Syntax says
92-
that a 7-only cmdlet, parameter or -Parallel fails where it stands and the script carries
93-
on, and flags Out-File -Encoding utf8NoBOM, which was listed and never matched;
94-
IslInteractiveCall warns instead of erring when Get-Credential -Credential is handed
95-
something that may be a built credential; IslContextIssue's drive-letter finding is
96-
Information, since the letter cannot say whether it is a mapped drive.
97-
Repair-IntuneScript no longer turns 'return 1; exit 1' into '1; exit 0; exit 1' with no
98-
finding left. Help: what Invoke-ScriptAnalyzer -Severity does with the custom rules. See
99-
CHANGELOG.md.
100-
Earlier versions, 0.1.0 to 0.26.0: CHANGELOG.md, which ships with the module.
95+
Earlier versions, 0.1.0 to 0.27.0: CHANGELOG.md, which ships with the module.
10196
'@
10297
RequireLicenseAcceptance = $false
10398
}

0 commit comments

Comments
 (0)