Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 5 to 8

[dependabot]

Bumps PSModule/Process-PSModule/.github/workflows/workflow.yml from 5 to 8.

Release notes

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

v8.0.0

🌟 [Major]: Publish stable releases from default-branch pushes (#512)

Process-PSModule now authorizes stable module publication from an important push to the default branch rather than from a merged pull_request event. An associated merged pull request supplies labels and release notes only when its merge commit exactly matches the pushed SHA; direct pushes and default-branch manual dispatches release a Patch version with commit-based notes.

Breaking Changes

Caller workflows must add a push trigger for their default branch to receive stable releases. The canonical caller templates now use non-cancelling per-pull-request-or-ref concurrency so pull-request cleanup and the resulting default-branch release remain independent while all release mutations queue safely. The consumer-repository rollout remains tracked in #438.

Changed: Stable release lifecycle

• Open labelled pull requests can publish prereleases; closed pull requests run prerelease cleanup only.
• Important default-branch pushes run the full pipeline and publish a stable release only after PowerShell Gallery publication succeeds.
• GitHub releases and tags target the exact tested pushed commit.
• Direct default-branch pushes and manual dispatches default to Patch regardless of AutoPatching; pull-request prereleases retain their configured AutoPatching behavior.
• First pushes are evaluated from the complete Git tree, and truncated trees fail explicitly rather than producing an unsafe release decision.
• Only a real pull_request.closed event can enter cleanup; a label change on an already closed PR runs no build, prerelease, or cleanup path.
• Release workflow concurrency uses cancel-in-progress: false to preserve serialized artifact and tag mutation.

Dogfood and documentation

• The default and manifest dogfood callers now receive the complete PR event contract, including label changes and closure, and do not cancel release-capable runs.
• Fixture roots are important, fixture sites build, and Publish.Site.Skip prevents deployment to the Process-PSModule Pages environment.
• Caller, first-release, scenario, stage, settings, specification, and module-standard documentation now define default-branch push authority, cleanup-only closed PRs, direct-push behavior, and non-cancelling concurrency.

Scope boundary

Release-GHRepository@v2.0.3, which releases Process-PSModule itself, only supports pull-request event payloads. This PR therefore does not install a push trigger that would succeed without producing that repository release. Push-capable repository releases and moving workflow-consumer tags are tracked separately in PSModule/Release-GHRepository#108.

Technical Details

• The Plan settings action normalizes PR, push, and manual-dispatch state into a shared context.
• Push-to-PR association uses GET /repos/{owner}/{repo}/commits/{sha}/pulls and requires an exact merged commit match on the default branch.
• Version-label conflicts remain blocking for release decisions but cannot block closed-PR cleanup.
• Publishing, GitHub release creation, and cleanup receive the normalized PR context explicitly, so direct releases never attempt PR comments.
• Publish.Site.Skip separates site build from deployment; dogfood callers mark their fixture roots as important, build site artifacts, and skip real Pages publication.

• Fixes #390
• Related: #438
• Dependency: PSModule/Release-GHRepository#108

v7.0.0

🌟 [Major]: Reusable workflows now use GitHub App orchestration and explicit publish credentials (#408)

Process-PSModule now performs repository inspection, versioning, release management, and pull-request feedback through a configured GitHub App. Publishing uses the explicit PSGALLERY_API_KEY credential consistently from the reusable workflow through the publishing action.

... (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: 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.