Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.5.7 to 8.0.3

[dependabot]

Bumps PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.5.7 to 8.0.3.

Release notes

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

v8.0.3

Upgrade Process-PSModule to Pester 6.1 (#519)

Implemented in Process-PSModule

• Enforce the Pester [6.1.0,7.0.0) range in reusable framework test runs.
• Align module-local workflow inputs with the current Invoke-Pester contract: Version/Prerelease select Pester, while GitHubVersion/GitHubPrerelease select the GitHub module. Pester prerelease remains at the action default.
• Keep the six Test-PSModule container/test files inside the action implementation at .github/actions/Test-PSModule/src/tests, because they are context-dependent framework suites executed against the compiled module or source tree. Discovery remains $PSScriptRoot/tests/$settings.
• Add a framework CI contract test that validates Pester 6.1 configuration properties:
  • Run.Shuffle
  • Run.ShuffleSeed
  • Run.Parallel
  • Run.ParallelThrottleLimit
  • Debug.ShowStartMarkers
• Align coverage input documentation with Pester 6.1: supported formats are JaCoCo and Cobertura, and profiler-based tracing is documented correctly.
• Update Pester 6.1 authoring and coverage-report guidance.

Pester 6.1 runtime audit

A local Pester 6.1 probe generated a passing test result and coverage report, and the Get-PesterCodeCoverage action processed that JSON successfully. The coverage result shape remains compatible: CoveragePercent, CoveragePercentTarget, CommandsMissed, CommandsExecuted, FilesAnalyzed, and all count properties are present and consumed correctly.

The Pester result still exposes Containers; each container retains Data, Blocks, and aggregate result/count properties. The existing container files therefore remain compatible with the compiled-module/source-tree execution model.

Contract findings and required upstream follow-up

The current PSModule/Invoke-Pester v5.1.0 action does not expose these Pester configuration properties as action inputs, so this repository deliberately does not add incompatible passthrough mappings:

• Run_Shuffle
• Run_ShuffleSeed
• Run_Parallel
• Run_ParallelThrottleLimit
• Debug_ShowStartMarkers

The coordinated PSModule/Invoke-Pester follow-up must add each input to action.yml, forward each PSMODULE_INVOKE_PESTER_INPUT_* environment variable, map them into the generated PesterConfiguration, and publish a version/tag that Process-PSModule can pin. Process-PSModule can then expose the corresponding reusable-action inputs and pass them through.

Test and fixture boundaries confirmed

• Module-local tests assume the built module is already loaded: Test-ModuleLocal.yml imports the artifact in its prescript before invoking Pester.
• Framework module tests import the module explicitly in their own test scopes; no implicit preload was introduced.
• PSD1 files in the repository test fixture (src/data/Config.psd1 and src/data/Settings.psd1) are not implicitly loaded and are currently unused. Any future PSD1 dataset test must call Import-PowerShellDataFile explicitly or load it from supported setup.
• Expose-TestData passes only explicit caller-provided fixtures as environment variables to setup, teardown, and tests.
• Module linting remains a separate Invoke-ScriptAnalyzer job and artifact path; it is not folded into Pester execution.

Validation

• Pester 6.1 configuration contract validated locally.
• Pester 6.1 result/container and coverage shapes inspected locally.
• Get-PesterCodeCoverage executed against a generated Pester 6.1 coverage JSON fixture and passed.
• Restored Test-PSModule scripts parsed successfully.
• Test-PSModule path resolution validated from a consumer repository root.

... (truncated)

Commits

• 16419d0 Upgrade Process-PSModule to Pester 6.1 (#519)
• 7c8bc79 fix: Skip docs verification for closed pull requests (#522)
• bb49389 🪲 [Fix]: Obsolete GitHub token write permissions removed (#521)
• 8414050 Bump the github-actions group with 2 updates (#511)
• 5a11e8e 🌟 [Major]: Publish stable releases from default-branch pushes (#512)
• 68a2a7f 🌟 [Major]: Reusable workflows now use GitHub App orchestration and explicit p...
• 15c2814 ⚙️ [Maintenance]: Publish and release execution paths are now decoupled (#407)
• 120554a 📖 [Docs]: Process-PSModule owns the documentation root (#452)
• aa89bbe 📖 [Docs]: Process-PSModule documentation is now organized by task (#448)
• d1e2feb 📖 [Docs]: Process documentation publishes from Process-PSModule (#447)
• Additional commits viewable 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.