Repository navigation
Stabilize PowerShell CI against Pester drift - #7
Merged
Merged
Conversation
Replace deprecated mock assertions with the supported Should -Invoke form and pin the CI Pester version so GitHub Actions does not silently pick up breaking major-version changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Assert-MockCalledassertions withShould -Invoke6.1.0so GitHub Actions does not drift over timeCONTRIBUTING.mdWhy
The
masterCI failure on August 29, 2026 was caused by workflow-time dependency drift rather than by theactions/checkout@v7PR itself. The Windows tests had started installing Pester 6, while two tests still relied on legacy mock assertions that this PR updates to the supportedShould -Invokeform.Verification
6.1.0PowerShell static + unit tests passed6.1.0integration tests passed