Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.4.3 to 5.4.7

[dependabot]

Bumps PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.4.3 to 5.4.7.

Release notes

Sourced from PSModule/Process-PSModule/.github/workflows/workflow.yml's releases.

v5.4.7

🩹 [Patch]: Framework-generated code coverage no longer penalizes module authors (#310)

Framework-generated boilerplate — type accelerator registration and OnRemove cleanup — is now tested and covered by updated action versions referenced in this workflow. The obsolete $IsWindows PS 5.1 shim is no longer injected into built modules. Coverage from the framework test step and the module test step is already aggregated by Get-CodeCoverage, so module authors' coverage percentages now reflect only the code they wrote.

• Fixes #309

Changed: Build-PSModule updated to v4.0.14

Built modules no longer include the $IsWindows = $true Desktop edition shim or its PSScriptAnalyzer suppression attributes. PSModule targets PowerShell LTS (7.6+), where $IsWindows is a built-in automatic variable.

See PSModule/Build-PSModule#132 for details.

Changed: Test-PSModule updated to v3.0.10

The framework module tests now validate that every public class and enum is registered as a type accelerator after import, and that the OnRemove hook cleans them up when the module is removed. These tests produce coverage artifacts that are aggregated with module author test coverage, so framework-generated boilerplate no longer counts against the module author's coverage target.

See PSModule/Test-PSModule#113 for details.

Changed: README documents the framework testing design

The README now explains:

• Why framework-generated code is tested by the framework itself
• How coverage from both the framework test step and the module test step is aggregated
• That module authors do not need to test framework-generated code themselves

Technical Details

• .github/workflows/Build-Module.yml: Updated Build-PSModule from v4.0.13 to v4.0.14 (345728124d201f371a8b0f1aacb98f89000a06dc)
• .github/workflows/Test-Module.yml: Updated Test-PSModule from v3.0.8 to v3.0.10 (8c3337136dc7cf320da39eeb50e776d04bc9ac73)
• .github/workflows/Test-SourceCode.yml: Updated Test-PSModule from v3.0.8 to v3.0.10
• README.md: Added "Code coverage for framework-generated code" paragraph under the Framework test section; added coverage aggregation details under the Get code coverage section; removed reference to the $IsWindows shim
• No workflow structure changes — code coverage was already enabled in Test-Module.yml and Get-PesterCodeCoverage already aggregates all *-CodeCoverage artifacts

v5.4.6

🪲 [Fix]: Super-linter can now post PR comment summaries (#308)

Super-linter's inline PR comment summaries now appear when lint errors are found. Previously, the linter detected issues but silently failed to post the summary comment, requiring developers to navigate to the Actions log to see what went wrong.

• Fixes #307

Fixed: Lint error summaries now visible directly on PRs

When super-linter detects markdown, YAML, or other linting issues, it posts a summary comment on the pull request for quick feedback. This was failing with a 403 error because the Lint-Repository.yml reusable workflow's permissions: block only granted contents: read and statuses: write, omitting the pull-requests: write permission needed by the GitHub Issues API to create comments.

The error looked like this in the Actions log:

[WARN] Failed to call GitHub API: curl: (22) The requested URL returned error: 403
[WARN] Failed to create GitHub issue comment
</tr></table> 

... (truncated)

Commits

• 1111791 🚀 [Feature]: Release-triggering file patterns now configurable via workflow i...
• 3ed96da 🩹 [Patch]: Framework-generated code coverage no longer penalizes module autho...
• 205d193 🪲 [Fix]: Super-linter can now post PR comment summaries (#308)
• 4343d76 🩹 [Patch]: Setup/teardown jobs no longer waste runner time when scripts are a...
• 645cb19 🩹 [Patch]: Workflow dependencies updated to latest versions (#298)
• b849acd 📖 [Docs]: Module dependency declaration using #Requires -Modules now document...
• 2fb6675 📖 [Docs]: Add best practices for shared test infrastructure (#285)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[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