Bump PSModule/Invoke-Pester from 5.1.0 to 5.1.1

[dependabot]

Bumps PSModule/Invoke-Pester from 5.1.0 to 5.1.1.

Release notes

Sourced from PSModule/Invoke-Pester's releases.

v5.1.1

🪲 [Fix]: Configured Pester report paths now work (#78)

Configured Pester report paths now determine where the action writes test-result and code-coverage reports. Workflows that leave either path unset retain that report's established default location.

Fixed: Pester report paths ignore configuration

The action now honors TestResult.OutputPath and CodeCoverage.OutputPath values supplied through a Pester configuration file or the matching TestResult_OutputPath and CodeCoverage_OutputPath action inputs. Direct action inputs continue to override configuration-file values, and each path can be configured independently.

with:
  TestResult_OutputPath: .PSModule/TestResult/results.xml
  CodeCoverage_OutputPath: .PSModule/CodeCoverage/coverage.xml

Adopting this release

1. Select the published release of this action through the existing workflow reference.
2. Set either output-path input, or its equivalent Pester configuration property, when that report should use a custom destination. Keep direct inputs only when they are intended to override the configuration file.
3. Leave a setting unset to retain that report's established default location. No configuration change is required for workflows that use the default locations.

Release impact

Field	Value
Effective decision	release:patch, selected as a backward-compatible correction to existing report-path configuration.
Semantic effect	Patch, stable; existing configurations now write reports to their configured locations, while omitted settings retain their prior defaults.
Release/base coordinates	The release process resolves the final target version, tag, immutable source, version-computation base, and release/source baseline at publication.

---

Consumer change record

Identifier / surface	Before	After	Applicability / prerequisites	Consumer action	Verification
REPORT-PATH-CONFIG / TestResult.OutputPath and CodeCoverage.OutputPath	Values supplied through a Pester configuration file or the matching action inputs were overwritten with action-generated default paths.	Configured report paths are retained; direct action inputs override configuration-file values; each omitted path retains its established default location. JSON companion files use the same base name with a .json extension without overwriting non-XML report names.	Action consumers that configure either Pester report path.	Set only the paths that should use custom destinations; no edit is required when using the default locations.	The output-path action-test matrix covers defaults, configuration-file values, direct inputs, input precedence, independent overrides, and non-XML extensions. Each scenario asserts the generated report and JSON locations.
ACTION-TEMP-STATE / generated configuration and containers	Internal handoff files were created in .temp beneath the action working directory.	Each invocation creates an isolated subdirectory beneath the platform temporary directory's Invoke-Pester folder and exposes it as TempPath.	Hosts supported by PowerShell and .NET temporary-path resolution.	No consumer edit required.	A sequential two-invocation action test verifies distinct TempPath values and separate handoff configurations.

Template baseline

Not applicable: Invoke-Pester is consumed as a GitHub Action and this release does not distribute an integration template. The action-level workflow validates the pull request source.

Maintainer evidence

• src/init.ps1 retains explicitly configured report paths, supplies the historical defaults only when a path is absent, and normalizes final report paths for artifact upload.
• action.yml, src/init.ps1, and src/exec.ps1 pass one invocation-specific TempPath through the action-private handoff lifecycle.
• src/exec.ps1 uses Path.ChangeExtension for separate JSON companion reports.
• README.md documents the existing Pester report-path inputs and the TempPath output; the action-test workflow covers default, configured, precedence, independent-override, non-XML, and temporary-isolation behavior.

... (truncated)

Commits

• c5494ab 🪲 [Fix]: Configured Pester report paths now work (#78)
• 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: github-actions. Please create it before Dependabot can add it to a pull request.

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