Plan job fails on schedule/workflow_dispatch: Resolve-Version requires a pull_request event (v6.1.0+ regression)

[MariusStorhaug]

Summary

Since v6.1.0 (#342, which moved version resolution into the new Plan job), the Plan job fails on any event that is not pull_request. The Resolve-Version step (PSModule/Resolve-PSModuleVersion@v1.1.0) throws:

Exception: GitHub event does not contain pull_request data. This action must be run from a pull_request event.

Because every downstream job needs: Plan, the whole run fails on schedule and workflow_dispatch events.

Impact

The reusable workflow's own recommended caller (README) and PSModule/Template-PSModule both trigger on workflow_dispatch, schedule (daily cron), and pull_request. On v6.1.0/v6.1.1 the scheduled and manual runs now fail for every consumer. pull_request events are unaffected.

Evidence

• Process-PSModule self-test Workflow-Test [Default]:
  • 2026-07-09 schedule → success (pre-v6.1.0)
  • 2026-07-10 schedule → failure at Plan / Plan, Resolve-Version step (run 29060730986)
• PSModule/Template-PSModule workflow_dispatch on v6.1.1 → failure at Plan / Plan with the same exception (run 29085027012)

Root cause

.github/workflows/Plan.yml runs the Resolve-Version step unconditionally, but PSModule/Resolve-PSModuleVersion requires pull_request event data.

Suggested fix

One of:

• Gate the Resolve-Version step in Plan.yml with if: github.event_name == 'pull_request', and have Enrich-Settings fall back to safe Settings.Module.* defaults for non-PR events; or
• Make Resolve-PSModuleVersion a no-op (e.g. resolve 0.0.0) on non-pull_request events instead of throwing.

Either keep schedule / workflow_dispatch working (they still run build/test), or update the README caller example and Template-PSModule to drop those triggers.

[MariusStorhaug]

Fixed in #375.

Approach: gate the Resolve-Version step in Plan.yml to pull_request events. On non-PR events (schedule / workflow_dispatch / push) ReleaseType already resolves to None, Run.PublishModule is already false, and Enrich-Settings falls back to safe empty version defaults — so the run does its build/test work without crashing. Release-on-merge-to-default-branch and prerelease-on-prerelease-labeled-PR are unchanged.

A literal push: [main] release trigger (which would require changes to Get-PSModuleSettings + Resolve-PSModuleVersion + every caller) was considered but is not needed to fix this — releases already happen when a PR merges to the default branch.

Validated on the fix branch:

• workflow_dispatch self-test: Plan now succeeds (was failing at Resolve-Version), build/test proceed.
• PR self-test (pull_request): Resolve-Version still runs and succeeds — version resolution path intact.