Skip to content

Commit 664b64a

Browse files
authored
Merge pull request #27 from fadwen/release/v0.29.0
release: 0.29.0
2 parents a87c25e + 513a0d6 commit 664b64a

2 files changed

Lines changed: 24 additions & 21 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,20 +11,27 @@ release notes.
1111

1212
## [Unreleased]
1313

14-
### Fixed
14+
Nothing yet.
1515

16-
- **`Invoke-IntuneRemediationTest` reported Recurred for a remediation that writes to stderr and exits 0.** On
17-
the device that run is a script error: `RemediationStatus` 3, Graph `remediationState` `scriptError`, the
18-
error text attached, no post-detection. The harness now reports Failed, skips the post-detection and warns
19-
that the exit code was 0. A detection that writes to stderr and exits 0 is still Without issues, as before.
20-
Measured in user context on the lab device with five one-off remediations (round 11, `REM-STDERR-*`).
16+
## [0.29.0] - 2026-10-07
17+
18+
One finding from a real device, found by running a blog post's example through Intune: a remediation that
19+
writes to stderr is a script error whatever its exit code, and the harness had said Recurred since round 1.
20+
The harness, a rule, the evidence and the help follow the device now.
2121

2222
### Added
2323

2424
- `IslOutputIssue` warns about `Write-Error` and an unguarded cmdlet in a remediation script, the way it did
2525
for Win32 detection scripts, since either makes the agent report a script error instead of running the
2626
post-detection; the unguarded cmdlet carries `-ErrorAction Stop` as its fix.
2727

28+
### Fixed
29+
30+
- **`Invoke-IntuneRemediationTest` reported Recurred for a remediation that writes to stderr and exits 0.** On
31+
the device that run is a script error: `RemediationStatus` 3, Graph `remediationState` `scriptError`, the
32+
error text attached, no post-detection. The harness now reports Failed, skips the post-detection and warns
33+
that the exit code was 0. A detection that writes to stderr and exits 0 is still Without issues, as before.
34+
Measured in user context on the lab device with five one-off remediations (round 11, `REM-STDERR-*`).
2835
## [0.28.0] - 2026-10-06
2936

3037
Two commands run several times faster, the fixer applies eight more edits, the Graph calls are retried
@@ -556,7 +563,8 @@ Nothing any command does has changed.
556563

557564
- Static rules: `Test-IntuneScript`.
558565

559-
[Unreleased]: https://github.com/fadwen/IntuneScriptLab/compare/v0.28.0...HEAD
566+
[Unreleased]: https://github.com/fadwen/IntuneScriptLab/compare/v0.29.0...HEAD
567+
[0.29.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.28.0...v0.29.0
560568
[0.28.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.27.0...v0.28.0
561569
[0.27.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.26.0...v0.27.0
562570
[0.26.0]: https://github.com/fadwen/IntuneScriptLab/compare/v0.25.0...v0.26.0

‎IntuneScriptLab.psd1‎

Lines changed: 9 additions & 14 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.28.0'
4+
ModuleVersion = '0.29.0'
55
GUID = '3f6b2c9e-7d41-4a8f-9c2b-5e0d8a1f4b76'
66
Author = 'Jeffrey Stuhr'
77
CompanyName = ''
@@ -64,6 +64,13 @@ 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.29.0 - A remediation that writes to stderr is a script error on the device whatever its exit code:
68+
RemediationStatus 3, Graph scriptError, the error text attached, no post-detection.
69+
Invoke-IntuneRemediationTest reported Recurred for that run since round 1; it reports Failed,
70+
skips the post-detection and warns that the exit code was 0. A detection's stderr still changes
71+
nothing. IslOutputIssue warns about Write-Error and an unguarded cmdlet in a remediation script,
72+
with -ErrorAction Stop as the fix. Measured in user context on the lab device with five one-off
73+
remediations, recorded as round 11 (REM-STDERR-*). See CHANGELOG.md.
6774
0.28.0 - Test-IntuneScript analyzes a script about two and a half times faster, with the syntax tree
6875
walked once and indexed instead of once per rule; Get-IntuneAgentLog reads a large log
6976
filtered in a fifth of the time. Repair-IntuneScript takes -Context, -Architecture and
@@ -90,19 +97,7 @@ pre-flight over the tenant's deployed scripts and readers for the agent's logs
9097
Repair-IntuneScript no longer turns 'return 1; exit 1' into '1; exit 0; exit 1' with no
9198
finding left. Help: what Invoke-ScriptAnalyzer -Severity does with the custom rules. See
9299
CHANGELOG.md.
93-
0.26.0 - Every claim in the README, help, about topic, rule reference and examples was checked
94-
against the code and by running it, and what did not hold was fixed: -Settings never
95-
reached the pre-flight or the drift compare; -Id alone selected every policy;
96-
Repair-IntuneScript -WhatIf on a folder returned nothing; the encoding fix corrupted
97-
ANSI files; a directive earned the assumed-context note; a settings file's ExcludeRule
98-
beat an explicit -IncludeRule; Should-PassIntuneAnalysis failed on a pipeline of files;
99-
SARIF rule levels, outside-root URIs and relative output paths; a missing script path
100-
returned a result; timeline -Id and relationship reports; case-insensitive drift
101-
compare; All devices for a user-context app; -SkipAnalysis hiding 'assigned to nobody';
102-
-ne/-notIn filter values; a bare -Confirm; Stop as a guard; using module and two
103-
parameters in the PowerShell 7 rule; Win32 scripts in the size rule. Help corrected
104-
throughout. See CHANGELOG.md.
105-
Earlier versions, 0.1.0 to 0.25.0: CHANGELOG.md, which ships with the module.
100+
Earlier versions, 0.1.0 to 0.26.0: CHANGELOG.md, which ships with the module.
106101
'@
107102
RequireLicenseAcceptance = $false
108103
}

0 commit comments

Comments
 (0)