⚙️ [Maintenance]: Lock Pester test dependency to the 6.x major version

[Marius Storhaug (MariusStorhaug)]

Modules scaffolded from this template now inherit a Pester 6.x major-version requirement in their test file, so every new module starts aligned with the rest of the ecosystem.

Changed: the module test template requires Pester 6.x

tests/PSModuleTest.Tests.ps1 now starts with:

#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }

Any Pester 6.x satisfies it; adopting a new major stays a deliberate change.

Technical Details

• Adds a #Requires -Modules statement to the template's test file. Module-identity (GUID) pinning is intentionally omitted — a separate supply-chain control, not part of the lock-to-major risk appetite.
• The install side is locked to the same major in ⚙️ [Maintenance]: Lock Pester to the 6.x major version Invoke-Pester#70. Part of the dependency-management epic Dependency management for PowerShell scripts and modules Process-PSModule#356.

[github-actions]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Path	Description
src/**	Module source code
README.md	Documentation

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.

[github-actions]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Path	Description
src/**	Module source code
README.md	Documentation

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.

[github-actions]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Path	Description
src/**	Module source code
README.md	Documentation

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.

[github-actions]

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern	Description
^src/	Matches files where path matches this pattern
^README\.md$	Matches files where path matches this pattern

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.

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter