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

v5.5.0

🚀 [Feature]: Release-triggering file patterns now configurable via workflow input (#301)

Repositories can now control which file changes trigger build, test, and publish stages by configuring the ImportantFilePatterns workflow input or settings file property. The default patterns (^src/ and ^README\.md$) remain unchanged for backward compatibility.

• Fixes #278

New: Configurable release-triggering file patterns

The ImportantFilePatterns input is now available on the workflow.yml and Get-Settings.yml reusable workflows. Pass a newline-separated list of regex patterns to override the defaults:

jobs:
  Process:
    uses: PSModule/Process-PSModule/.github/workflows/workflow.yml@v5
    with:
      ImportantFilePatterns: |
        ^src/
        ^README\.md$
        ^examples/

To disable file-change triggering entirely, pass an empty string via the workflow input or set an empty list in .github/PSModule.yml:

# In .github/PSModule.yml
ImportantFilePatterns: []

Resolution order: settings file → workflow input → workflow input default values.

Changed: PR comment reflects configured patterns

The automated comment posted on PRs when no important files are changed now dynamically lists the configured patterns instead of a hardcoded table.

Technical Details

• Added ImportantFilePatterns input (type: string, newline-separated) to both .github/workflows/workflow.yml and .github/workflows/Get-Settings.yml with explicit defaults (^src/ and ^README\.md$).
• Bumped Get-PSModuleSettings action reference from v1.4.4 to v1.5.0 which implements the settings file and action input support for this feature.
• Passed ImportantFilePatterns input through the reusable workflow chain to the Get-PSModuleSettings action step.
• Updated README documentation: new input in the workflow inputs table, new "Customizing important file patterns" section with YAML examples, updated settings file reference and example schema.

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

... (truncated)

• 1111791 🚀 [Feature]: Release-triggering file patterns now configurable via workflow i...
• 3ed96da 🩹 [Patch]: Framework-generated code coverage no longer penalizes module autho...
• See full diff in compare view

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)