Skip to content

📖 [Docs]: PowerShell module support aligned to latest LTS #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Marius Storhaug (MariusStorhaug) merged 2 commits into from
Jul 25, 2026
+5 −2
Merged

📖 [Docs]: PowerShell module support aligned to latest LTS #86

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e26f673
Clarify latest LTS support policy
MariusStorhaug Jul 25, 2026
d2dc1af
Remove ternary restriction from module standard
MariusStorhaug Jul 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions src/docs/Modules/Standards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,11 @@

Standards for implementing and reviewing PowerShell modules in the PSModule organization. These rules apply to modules built with the [PSModule framework](https://github.com/PSModule/Process-PSModule).

For general PowerShell coding standards (naming, style, function structure, documentation, readability, error handling), see [PowerShell Standards](../Standard/index.md). This page covers only module-specific conventions.
For general PowerShell coding standards (naming, style, function structure, documentation, readability, error handling), see [PowerShell Standards](../PowerShell/Standard/index.md). This page covers only module-specific conventions.

## Supported PowerShell version

PSModule modules support only the latest PowerShell Long Term Support (LTS) release. Do not preserve compatibility with Windows PowerShell 5.1; use language and platform capabilities available in the latest LTS when they improve the implementation.

> **Repo-local config wins.** Repo-level `.github/linters/.powershell-psscriptanalyzer.psd1` and `.github/PSModule.yml` override anything below. This standard fills the gap.

Expand Down Expand Up @@ -312,7 +316,6 @@ The CI pipeline automatically tests every source file against the following rule
| `NumberOfProcessors` | Use `[System.Environment]::ProcessorCount`, not `$env:NUMBER_OF_PROCESSORS` |
| `Verbose` | Do not pass `-Verbose` to commands unless explicitly silenced with `-Verbose:$false` |
| `OutNull` | Use `$null = ...` instead of `\| Out-Null` |
| `NoTernary` | No ternary operators — maintain PowerShell 5.1 compatibility |
| `LowercaseKeywords` | All PowerShell keywords must be lowercase |
| `FunctionCount` | Each file must contain exactly one function or filter |
| `FunctionName` | Filename must match the function or filter name |
Expand Down