Skip to content

Prepare v2.3.0: CHANGELOG release section and upgrade note #93

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
spydisec merged 2 commits into from
Oct 2, 2026
Merged

Prepare v2.3.0: CHANGELOG release section and upgrade note #93

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9377934
Prepare v2.3.0: CHANGELOG release section and upgrade note
spydisec Oct 2, 2026
50deefb
Prepare v2.3.0: cite Microsoft's transcription policy guidance in the…
spydisec Oct 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,17 @@ Releases are tagged `vX.Y.Z` and published with a zip and a SHA256 checksum.

## [Unreleased]

## [2.3.0] - 2026-10-02

One new read-only check: `Test-LoggingBaseline.ps1` now reports the PowerShell transcription policy, which the kit never sets. No setting or script behaviour changes otherwise.

**Upgrading from 2.2.2**

| If you used | Now |
|---|---|
| `Test-LoggingBaseline.ps1` in a pipeline or RMM check | A host with transcription on and no `OutputDirectory` now fails (exit 1) where it passed before. Fix the policy, not the kit: set an `OutputDirectory` with restricted access (per [Microsoft's PowerShell Group Policy settings](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_group_policy_settings#turn-on-powershell-transcription)), or remove the `Transcription` policy key. Transcription that is directed to a folder passes with a note. |
| Anything else | Nothing to do. |

### Added

- 🧾 **Transcription policy check.** `Test-LoggingBaseline.ps1` now has a read-only Safety row for the PowerShell transcription policy, which the kit never sets. On with no `OutputDirectory` fails, because every session then writes a transcript into the user's Documents folder; on with a folder passes with a note; off passes. Machine policy takes precedence; the user policy of the account running the test is read when no machine policy is set, and a `Wow6432Node` copy that disagrees is noted. The Safety never-do table explains it. [#91](https://github.com/spydisec/WinLogKit/issues/91)
Expand Down
Loading