🌟 [Major]: Support push-authoritative releases and moving workflow tags

[MariusStorhaug]

Outcome

Release-GHRepository can create a stable repository release from an important push to the default branch and maintain the moving workflow-consumer tags for that release.

Context

PSModule/Process-PSModule#512 moves module publication to default-branch pushes. Its repository-release workflow initially added the same trigger, but Release-GHRepository@v2.0.3 exits whenever the event payload has no pull_request. Leaving that trigger in place would make an important push report success without creating the Process-PSModule workflow release.

The caller workflow is itself a versioned delivery surface. Consumers must be able to reference its compatible moving major channel (for example, @v5) after an immutable release succeeds.

Acceptance criteria

• A default-branch push can create a stable release without a pull_request event payload.
• When the pushed SHA is exactly the merge commit of a default-branch pull request, its labels, title, and body provide the release bump and notes.
• A direct default-branch push and manual default-branch dispatch use a safe Patch fallback with commit-based notes.
• Closed pull requests retain prerelease cleanup behavior but cannot create stable releases.
• The GitHub Release and immutable version tag target the exact pushed SHA.
• After a stable release succeeds, moving v<major>, v<major>.<minor>, and latest tags are updated atomically to that immutable release commit.
• Tests cover merged-PR, direct-push, manual-dispatch, and closed-PR event contexts.

Related

• Blocks restoring push-triggered repository releases in 🌟 [Major]: Publish stable releases from default-branch pushes Process-PSModule#512.