@@ -13,6 +13,88 @@ release notes.
1313
1414Nothing yet.
1515
16+ ## [ 0.26.0] - 2026-09-28
17+
18+ Every claim the module makes, in its README, help, about topic, rule reference, examples and
19+ changelog, was checked against the code and by running it. What follows is what did not hold.
20+
21+ ### Fixed
22+
23+ - ** ` -Settings ` never reached the analysis.** ` Test-IntuneDeployedScript ` and
24+ ` Compare-IntuneDeployedScript ` overwrote their ` Settings ` parameter with a body-level
25+ ` $settings ` hashtable (variable names are case-insensitive) and then tested
26+ ` $PSBoundParameters ` inside a nested function, where it is that function's own. The
27+ pre-flight ran its normal settings-file search instead, and the drift compare ignored the
28+ hashtable. ` Get-IntuneScriptHealth ` forwarded the parameter to both, so it lost it too.
29+ - ** ` -Id ` on its own selected every policy** in the three Graph commands, because ` -Name `
30+ defaults to ` * ` and selection was name or id. ` -Id ` alone now selects by id.
31+ - ** ` Repair-IntuneScript -Path <folder> -WhatIf ` returned nothing.** The folder was enumerated
32+ through ` ForEach-Object -MemberName ` , which honours ` -WhatIf ` . ` Test-IntuneScript ` had the
33+ same construct and returned no findings for a folder while ` $WhatIfPreference ` was set.
34+ - ** The encoding fix corrupted ANSI files.** A BOM-less file that was not UTF-8 was decoded as
35+ UTF-8 and written back with every non-ASCII character replaced by U+FFFD. Repair now reads
36+ such a file in the system ANSI code page, and ` IslEncodingIssue ` reports it as ANSI
37+ (Information) rather than as UTF-8 without a BOM.
38+ - ** A type declared in a directive earned the assumed-context note** and was called a portal
39+ default. A directive is a declaration; the note is for inferred types only.
40+ - ** A settings file's ` ExcludeRule ` beat an explicit ` -IncludeRule ` .** An explicit include now
41+ sets the file's exclusions aside; ` -ExcludeRule ` still adds to them.
42+ - ** ` Should-PassIntuneAnalysis ` failed on a pipeline of files** , joining their paths into one.
43+ It now analyzes every file and names the ones that fail.
44+ - ** SARIF:** every rule was given the level ` warning ` ; it now carries the level of the most
45+ severe finding it produced in the log. A finding outside ` -Root ` was written as an escaped
46+ relative URI under the root; it is now an absolute file URI. A relative ` -Path ` was resolved
47+ against the process directory, as was ` Get-IntuneScriptHealth -MarkdownPath ` .
48+ - ** A missing script path** made the harness return a result with a made-up exit code instead
49+ of an error.
50+ - ** ` Get-IntuneAgentTimeline -Id ` ** returned every timeline whose lines mentioned the id (a
51+ relationship report names two apps); it now returns the timeline whose own id it is. A
52+ relationship report is an outcome.
53+ - ** ` Compare-IntuneDeployedScript ` ** compared content without regard to case, so a change in
54+ letter case only came back as "the bytes differ outside the UTF-8 text".
55+ - ** A user-context Win32 app assigned to All devices** was not flagged, only one assigned to a
56+ device group.
57+ - ** ` Get-IntuneScriptHealth -SkipAnalysis ` ** called an unassigned policy Healthy, because the
58+ check read a finding. It now reads the assignments.
59+ - ** ` IslFilterIssue ` ** called ` -ne ` and ` -notIn ` with a value no device reports "never matches";
60+ such a clause matches every device, and is reported so, as Information.
61+ - ** ` IslInteractiveCall ` ** took a bare ` -Confirm ` , which forces the prompt, as silencing it.
62+ - ** ` IslOutputIssue ` ** took ` $ErrorActionPreference = 'Stop' ` as guarding a probing cmdlet;
63+ Stop puts the miss on stderr, which is the failure the rule warns about.
64+ - ** ` IslPowerShell7Syntax ` ** reported a ` using module ` the parser could not find as PowerShell 7
65+ syntax, and listed ` Get-Process -CommandLine ` and ` New-TemporaryFile -Extension ` , which exist
66+ on neither host.
67+ - ** ` IslScriptSize ` ** called Win32 detection and requirement scripts remediations; it now names
68+ them and says the remediation limits are assumed for them, since only remediations and
69+ platform scripts were measured.
70+ - ** A stored-password task the scheduler never launches** made the harness wait out the whole
71+ timeout. For an account without the "Log on as a batch job" right the lab device no longer
72+ answers ` 0x80070569 ` ; the task sits Ready with ` 0x00041303 ` ("has not run yet") and no error
73+ anywhere. Five seconds of that is now reported as the refusal, with the same hint.
74+ - ** ` Test-IntuneScript -EnforceSignatureCheck:$false ` ** was not explicit, so a tenant script's
75+ own directive could turn the check on under the pre-flight.
76+ - A typo in the ` IslContextIssue ` message; the AgentTimeline ` Duration ` column dropped days;
77+ the workflow template's runtime job did not split a comma-separated ` SCRIPT_PATHS ` .
78+
79+ ### Changed
80+
81+ - The reporting lag in ` Get-IntuneScriptHealth ` 's help is the measured one: a remediation's
82+ changed result reaches Graph with the agent's next hourly report batch (65 minutes after the
83+ run on 2026-09-29), a platform script's in 2-8 s, an app's in 30-39 s; an unchanged result is
84+ not re-reported, so ` lastStateUpdateDateTime ` is the last change. ` Get-IntuneAgentTimeline ` 's
85+ help gave the remediation report codes wrong: 3 is no issue, 4 is the remediation having run
86+ (fixed or not), 5 is a detection script failure.
87+ - The rule reference keeps literal names such as ` $PSScriptRoot ` in a message instead of
88+ replacing them with ` <value> ` .
89+ - The manifest description names the whole module; the README's links into the repository are
90+ absolute, since the README ships in the package and ` docs/ ` and ` Validation/ ` do not.
91+ - Help corrections throughout: what each result carries (` RunAs ` , ` IntuneError ` as the stderr
92+ tail, ` SignatureStatus ` always present), the complete status lists, the events
93+ ` Get-IntuneAgentLog ` names, the Id rule, what ` -SkipRegistry ` leaves out, the ARM64 note on
94+ the x64 default, the base requirements ` Test-IntuneWin32Requirement ` covers, how names are
95+ matched and which local files count as ` NotInTenant ` , the Attention rules, and the
96+ ` Applied ` count under ` -WhatIf ` .
97+
1698## [ 0.25.0] - 2026-09-28
1799
18100The first release from this repository, and the first published to the PowerShell Gallery.
@@ -280,5 +362,6 @@ Nothing any command does has changed.
280362
281363- Static rules: ` Test-IntuneScript ` .
282364
283- [ Unreleased ] : https://github.com/fadwen/IntuneScriptLab/compare/v0.25.0...HEAD
365+ [ Unreleased ] : https://github.com/fadwen/IntuneScriptLab/compare/v0.26.0...HEAD
366+ [ 0.26.0 ] : https://github.com/fadwen/IntuneScriptLab/compare/v0.25.0...v0.26.0
284367[ 0.25.0 ] : https://github.com/fadwen/IntuneScriptLab/releases/tag/v0.25.0
0 commit comments