Rename generic Helpers.psm1 helper modules to per-action names (Action.Helpers) across all actions

[MariusStorhaug]

Context

Per the naming standard in MSXOrg/docs (linked below), an action's private helper module must be named after the action (<ActionRepo>.Helpers) instead of the generic Helpers. A module named Helpers collides with the shared framework Helpers module (installed by PSModule/Install-PSModuleHelpers, and loaded into the test session by PSModule/Invoke-Pester). Two modules named Helpers in one session break module resolution and make Pester Mock -ModuleName Helpers ambiguous.

Concrete failure and fix template: PSModule/Resolve-PSModuleVersion#4 — renamed the helper module, updated the entry-script import and the test -ModuleName, and kept the framework Import-Module -Name 'Helpers' line. RuntimeException: Multiple script or manifest modules named 'Helpers' are currently loaded.

Scope — rename in every action repo that ships a generic helper module

Confirmed via org-wide code search (filename:Helpers.psm1 org:PSModule):

• Debug — src/Helpers.psm1 -> Debug.Helpers.psm1
• Get-PesterCodeCoverage — src/Helpers.psm1 -> Get-PesterCodeCoverage.Helpers.psm1
• Invoke-Pester — src/Helpers.psm1 -> Invoke-Pester.Helpers.psm1
• Resolve-PSModuleVersion — align the interim scripts/ResolveVersion.psm1 (from Lock workflow to use v0 of actions #4) to Resolve-PSModuleVersion.Helpers.psm1

Special case (do NOT blindly rename):

• Install-PSModuleHelpers — ships src/Helpers/Helpers.psm1, which is the shared canonical Helpers module imported across actions. Keep it named Helpers; document the carve-out.

Per-repo change checklist

For each affected action:

1. git mv the module file to <ActionRepo>.Helpers.psm1 (and the matching test file, if any).
2. Update the entry-script import path to Import-Module -Name "$PSScriptRoot/<ActionRepo>.Helpers.psm1", keeping the framework Import-Module -Name 'Helpers' line.
3. Update tests: -ModuleName '<ActionRepo>.Helpers' plus the module import path and any data-file path.
4. Verify CI green (Action-Test / Pester). The collision only reproduces where the framework Helpers is loaded, so validate locally by pre-loading a dummy module named Helpers before Invoke-Pester.
5. Release the action.

Audit for completeness

Code search only indexes default branches and files literally named Helpers.psm1. Before closing, audit all action repos (any repo with a root action.yml) for any helper/script module whose name is not <ActionRepo>.Helpers:

# per action repo (check scripts/ and src/)
gh api repos/PSModule/<repo>/contents/scripts --jq '.[].name'
gh api repos/PSModule/<repo>/contents/src --jq '.[].name'

Acceptance criteria

• Every PSModule action's private helper module is named <ActionRepo>.Helpers (except the documented Install-PSModuleHelpers carve-out).
• No action ships a module named Helpers except Install-PSModuleHelpers.
• All affected actions have green CI and a released version.
• Standard declared in MSXOrg/docs (see Related).

Related

• Standard declaration: PowerShell standard: name GitHub Action helper modules after the action (e.g. Build-PSModule.Helpers) MSXOrg/docs#24
• Fix template / first fix: 🚀 [Feature]: Version output always emitted regardless of publish decision Resolve-PSModuleVersion#4

[MariusStorhaug]

Rename PRs opened — CI green (Action-Test + Lint), awaiting review, not merged:

• Debug — 🩹 [Patch]: Name the helper module after the action (Debug.Helpers) Debug#32 (Helpers.psm1 → Debug.Helpers.psm1)
• Get-PesterCodeCoverage — 🩹 [Patch]: Name the helper module after the action (Get-PesterCodeCoverage.Helpers) Get-PesterCodeCoverage#22 (Helpers.psm1 → Get-PesterCodeCoverage.Helpers.psm1)
• Resolve-PSModuleVersion — 🩹 [Patch]: Name the helper module after the action (Resolve-PSModuleVersion.Helpers) Resolve-PSModuleVersion#8 (aligns the interim ResolveVersion.psm1 → Resolve-PSModuleVersion.Helpers.psm1)

Each is a pure rename + reference updates (entry-script import, tests -ModuleName), keeping the framework Import-Module -Name 'Helpers'. No runtime logic changed.

Deferred:

• Invoke-Pester — its open draft PR 🚀[Feature]: Add a linter test on the built module #71 already modifies src/Helpers.psm1, src/exec.ps1, and src/init.ps1 (the exact files a rename touches). To avoid conflicts, the rename should land with/after 🚀[Feature]: Add a linter test on the built module #71 or be folded into it.
• Install-PSModuleHelpers — carve-out, no change (it is the canonical shared Helpers module).

[MariusStorhaug]

Update: Invoke-Pester is no longer deferred — the rename is folded into its open PR #71 (per request) instead of a separate PR.

• Commit a7c2478 on feat/68-configurable-pester-version: src/Helpers.psm1 → src/Invoke-Pester.Helpers.psm1, with src/exec.ps1 and src/init.ps1 imports updated (framework Helpers/LogGroup usage kept).
• Full Action-Test matrix (1-Simple, 2-Standard, 3-Advanced, Pester 5.x/6.0.0 constraints) + linters green.
• Ships when 🌟 [Major]: Version and Prerelease inputs now control Pester Invoke-Pester#71 merges.

So all four actions are now covered: Debug#32, Get-PesterCodeCoverage#22, Resolve-PSModuleVersion#8 (standalone), and Invoke-Pester (in #71). Install-PSModuleHelpers remains the carve-out.

[MariusStorhaug]

All actions that shipped a generic Helpers module have been renamed to <Action>.Helpers, merged, and released:

Action	PR	Release	Module
Debug	#32	v1.0.9	Debug.Helpers
Get-PesterCodeCoverage	#22	v1.0.5	Get-PesterCodeCoverage.Helpers
Invoke-Pester	folded into #71	v5.1.0	Invoke-Pester.Helpers
Resolve-PSModuleVersion	#8	v1.1.3	Resolve-PSModuleVersion.Helpers

Install-PSModuleHelpers remains the canonical shared Helpers module (carve-out — no change). Standard declared in MSXOrg/docs#25.

All acceptance criteria met. Closing.