⚙️ [Maintenance]: Lock Pester test dependency to the 6.x major version#17
⚙️ [Maintenance]: Lock Pester test dependency to the 6.x major version#17Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
Conversation
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
There was a problem hiding this comment.
Pull request overview
Updates the test harness dependency declaration to accept any Pester 6.x release (while retaining the module GUID pin), reducing maintenance churn for minor/patch Pester updates.
Changes:
- Replaces a strict
RequiredVersion = '5.8.0'Pester pin with a 6.x major-version range usingModuleVersion+MaximumVersion. - Preserves the Pester module identity pin via
GUID.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
The GUID pins module identity (precise pinning), a stricter control than the lock-to-major risk appetite. Keep only the version range.
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
This module's Pester tests now lock to the 6.x major version instead of the exact
5.8.0pin. An exact pin breaks whenever the runner resolves a different Pester (as happened once 5.8.0 was superseded); a major lock tracks every 6.x release while still blocking an unvetted new major.Changed: the exact 5.8.0 pin becomes a 6.x major lock
Each
*.Tests.ps1file now requires:#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }Any Pester
6.xsatisfies it, so routine minor and patch updates no longer need a PR — only a new major does.Technical Details
#Requires -Modulesstatement in each test file undertests/fromRequiredVersion = '5.8.0'toModuleVersion = '6.0.0'; MaximumVersion = '6.*'.GUID) pinning is intentionally omitted — a separate supply-chain control, not part of the lock-to-major risk appetite.