📖 [Docs]: Configure retained releases and current PR feedback

[Marius Storhaug (MariusStorhaug)]

Module repositories can now configure Process-PSModule so default-branch releases are retained while pull-request feedback converges on the latest change.

Changed: Workflow concurrency

Add this workflow-level block to the caller workflow that invokes Process-PSModule:

concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
  queue: ${{ github.event_name == 'pull_request' && 'single' || 'max' }}
  cancel-in-progress: ${{ github.event_name == 'pull_request' }}

Default-branch pushes and workflow_dispatch releases retain the maximum native queue. Pull-request activity cancels and replaces obsolete work for that pull request. A pull_request.closed event cancels its remaining activity, then enters the reusable workflow's existing close path without delaying the resulting default-branch release.

Migration

1. In .github/workflows/Process-PSModule.yml, replace the existing concurrency block with the block above.
2. Keep the group exactly as shown. Do not prepend Process-PSModule-: the reusable workflow already uses that prefixed group, and caller and reusable groups must differ.
3. Retain the pull_request actions opened, reopened, synchronize, labeled, unlabeled, and closed. The closed action is required for prerelease cleanup.
4. Keep workflow_dispatch when manual production releases are supported; it joins the retained production queue automatically.

---

Technical details

• Updates the caller template, repository setup guide, framework specification/design references, and the dedicated trigger spec/design.
• The caller's group is intentionally unprefixed; github.workflow isolates it from other caller workflows in the repository, while avoiding the reusable workflow's existing Process-PSModule-... group.
• No reusable-workflow implementation, secret, input, or settings interface changes.
• Live GitHub Actions evidence: three competing production pushes completed serially; manual dispatch waited for production; rapid PR activity was canceled; and PR closure canceled activity before its close job completed. A conditional producer-level group failed under contended production admission before jobs began.
• Standards and framework alignment:

Changed surface	Standards checked	Framework documentation checked	Result
Caller templates and workflow examples	MSX documentation, YAML, and GitHub Actions	Reusable workflow concurrency behavior	Aligned
Trigger specification and design	MSX specification and design templates	Framework release and cleanup contracts	Aligned

• Issue convergence sweep: Add concurrency groups to workflow.yml to prevent racing publishes #321, Clean up prerelease GitHub Releases when a PR is abandoned #211, Include list of removed prereleases in cleanup notice #274, and Rename AutoCleanup to CleanupPrereleases for clearer naming #266 remain open because this documentation PR does not implement their runtime changes.

Relevant issues (or links)

Related work

• References Add concurrency groups to workflow.yml to prevent racing publishes #321 — concurrency implementation.
• References Clean up prerelease GitHub Releases when a PR is abandoned #211 — abandoned-PR cleanup.
• References Include list of removed prereleases in cleanup notice #274 — cleanup reporting.
• References Rename AutoCleanup to CleanupPrereleases for clearer naming #266 — setting rename remains out of scope.

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
CSS	Pass ✅
CSS_PRETTIER	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
HTML	Pass ✅
JAVASCRIPT_ES	Pass ✅
JAVASCRIPT_PRETTIER	Pass ✅
MARKDOWN	Pass ✅
NATURAL_LANGUAGE	Pass ✅
POWERSHELL	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter