Loop 013
The stale-safe batch release loop
A release-coordination workflow that excludes stale or unfinished work, combines valid changes, and ships complete artifacts from the latest integrated main.
Ready-to-use prompt
Copy the loop
Review pending changes and pull requests, exclude stale or unfinished work, combine the valid changes, and release them together.
Verify / stop
Only current, complete changes ship in the combined release.
The released revision is the latest integrated main that contains every selected change.
Context and guidance When to use it, steps, safety notes, and related loops
Use this when
Use this when several branches or pull requests may be ready at once and the release must avoid stale worktrees, partial overlays, and incomplete changes.
How to run it
- Fetch current repository and pull-request state, then inspect every candidate change for freshness, completeness, ownership, checks, and dependencies.
- Exclude stale, superseded, conflicting, or unfinished work and record why each candidate was omitted.
- Integrate the valid changes, rerun the combined checks, and select the newest main revision that contains the full batch.
- Release complete artifacts from a clean checkout, serialize the deployment, and verify production before closing the batch.
Why it works
Evaluating all candidates before integration prevents stale code from entering a release through convenience or worktree confusion. Releasing from integrated main proves the deployed artifact matches the reviewed batch.
Implementation note
The candidate diff selects what belongs in the batch, but deployment must use complete artifacts from the latest integrated main. Never deploy from a task worktree or partial file overlay.