Skip to content

📖 [Docs]: Document the Pester major-version lock for test files#57

Open
Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
mainfrom
maintenance/pester-major-lock
Open

📖 [Docs]: Document the Pester major-version lock for test files#57
Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
mainfrom
maintenance/pester-major-lock

Conversation

@MariusStorhaug

@MariusStorhaug Marius Storhaug (MariusStorhaug) commented Jul 7, 2026

Copy link
Copy Markdown
Member

The PowerShell Test Specification now documents how test files pin the Pester framework, so contributors declare the same major-version lock everywhere.

Changed: the Test Specification documents the Pester version lock

A new "Pester version" section shows the requirement each *.Tests.ps1 file declares:

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

It explains that any 6.x is accepted, that the Invoke-Pester action installs a matching version, and that GUID identity-pinning is an optional, separate control rather than part of the default lock.

Technical Details

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Super-linter summary

Language Validation result
CHECKOV Pass ✅
GITHUB_ACTIONS Pass ✅
GITHUB_ACTIONS_ZIZMOR Pass ✅
GITLEAKS Pass ✅
GIT_MERGE_CONFLICT_MARKERS Pass ✅
HTML Pass ✅
JAVASCRIPT_ES Pass ✅
JAVASCRIPT_PRETTIER 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant