⚙️ [Maintenance]: Require Pester 6.x in test files#32
Merged
Marius Storhaug (MariusStorhaug) merged 3 commits intoJul 9, 2026
Conversation
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 7, 2026 15:46
View session
There was a problem hiding this comment.
Pull request overview
Adds a PowerShell #Requires -Modules directive to the test script to enforce using Pester 6.x during test discovery/execution.
Changes:
- Added
#Requires -Modulesconstraint for the Pester module (intended to lock to major version 6). - Normalized the file header so the requirement precedes the
BeforeAllblock.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The GUID pins module identity (precise pinning), a stricter control than the lock-to-major risk appetite. Keep only the version range.
Marius Storhaug (MariusStorhaug)
pushed a commit
that referenced
this pull request
Jul 9, 2026
Bumps [PSModule/Invoke-Pester](https://github.com/PSModule/Invoke-Pester) from 4.2.4 to **5.1.0** — the latest release. This updates the original Dependabot PR (which targeted 4.2.5) straight to the current latest, since 4.2.5/4.2.6 and the 5.x line were all released while this PR sat open (auto-rebase was disabled after 30 days). Invoke-Pester is used only in the `Action-Test.yml` CI test workflow, so this change has **no runtime impact** on consumers of this action. ### Major version note (v5.0.0) The 5.0.0 release contains one breaking change: the `Version` and `Prerelease` inputs now control the **Pester** version instead of the internal GitHub bootstrap module, which moved to `GitHubVersion`/`GitHubPrerelease`. This workflow's Invoke-Pester step sets **neither** `Version` nor `Prerelease` (only `env: data`), so the breaking change does not apply. With no `Version` input, v5.x installs the latest available Pester by default — the per-repository `#Requires` declaration in the test files remains the safety net (see #32, which locks tests to Pester 6.x). ### v5.x highlights - **v5.0.0** — `Version`/`Prerelease` now select the Pester version (NuGet range syntax); GitHub bootstrap controls renamed to `GitHubVersion`/`GitHubPrerelease`; the loaded Pester version now matches the resolved version and is reported accurately. - **v5.1.0** — adds an optional `Guid` input to pin Pester by module identity (validated at install time). Additive, no impact here. Pinned by commit SHA per repository convention: `4ff33199141fdf22568990b6107fe3148ae93a1c # v5.1.0`. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 9, 2026 22:42
View session
Marius Storhaug (MariusStorhaug)
deleted the
maintenance/lock-pester-major-6
branch
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.
Pester tests in this module now require the Pester 6.x major version, so every contributor and CI run resolves the same major and a new Pester major can't slip in and break the suite. The tests previously declared no framework requirement and ran on whatever Pester happened to be installed.
Changed: tests are locked to the Pester 6.x major
Every
*.Tests.ps1file now starts with a version-bounded requirement:#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }Any Pester
6.xsatisfies it, so minor and patch releases flow in automatically while moving to a new major stays a deliberate, reviewed change. No module source or behaviour changes.Technical Details
#Requires -Modulesstatement to each test file undertests/; non-test files are untouched.ModuleVersion = '6.0.0'is the floor andMaximumVersion = '6.*'the wildcard major ceiling. Module-identity (GUID) pinning is intentionally omitted — it is a separate supply-chain control, not part of the lock-to-major risk appetite.