[goosewobbler]

Fixes #739

• Concurrency: in the template, ci-setup snippet and example, the standing PR's publish on merge and its retry label get a group per PR, so no other run can replace or cancel a queued publish. A merged release:immediate PR stays in the shared group with the updates, so the two don't write release/next at once. Other events on a closed PR run no job, so each gets a group of its own. Only a maintainer's edit on an open PR cancels.
• Branch-delete guard: publish deletes the branch with --force-with-lease pinned to the merged PR's head commit, so the remote refuses the delete if an update has force-pushed it since. If the head can't be read, publish keeps the branch and warns. Cleanup errors stay warnings. GitPushOptions.forceWithLease accepts a { ref, expect } lease, and the forge's PullRequestDetails carries headSha.
• immediate-release added to the ci-setup snippet and the example, reconciling with refresh-after-release.
• LLM keys move to the publishing jobs; update-release-pr needs one only for release:preview-notes. Docs and troubleshooting say so.
• Templates set up pnpm and use Node 24 (OIDC trusted publishing needs the newer npm), as does the release README's preview snippet. The npm hints say to drop pnpm/action-setup.
• immediate-release skips the standing PR itself (head release/next, hardcoded like the label names), so a standing PR carrying release:immediate doesn't publish twice. The in-step check for a renamed branch is Release gate: a merged standing PR carrying release:immediate is released twice #792.
• The example's immediate-release job removes the token .npmrc like its other publish jobs (whether that step is needed at all is Examples: drop the rm -f .npmrc step, which deletes the repo's own .npmrc rather than setup-node's #791). The ci-setup and example README text matches the new jobs.
• deleteBranchOnMerge's description says when publish keeps the branch.

The standing PR's publish and updates no longer wait for each other, so an update during a publish can double-bump until the next update. Tracked in #790.

Made with Cursor

Confidence Score: 3/5

The PR still needs changes before merging because branch cleanup can race an update and pending releases can still be dropped.

Summary

Updates the standing-PR workflows and adds a branch-tip check before publish cleanup.

• Publishing skips deleting a release branch that has moved since the manifest was written.
• Merged feeder pull requests can publish immediately and refresh the standing PR.
• Release workflow templates set up pnpm and run on newer Node versions.
• Workflow examples show where provider keys go for release-note generation.
• The workflow examples explain how publish and update runs share a queue.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Update release branch] --> B[Commit and push]
  B --> C[Read releaseBranchSha]
  C --> D[Save manifest in PR comment]
  D --> E[Publish from manifest]
  E --> F[Fetch origin]
  F --> G{Fetched tip matches saved SHA?}
  G -->|No| H[Keep branch]
  G -->|Yes| I[Push branch deletion]

Loading

_{Reviews (2) · Last reviewed commit: "fix(release): guard release branch delet..." · Reviewed by Greptile}

[github-actions]

Standing release PR: #730 · v0.42.1 queued (4 packages) · open 9h 25m · ✅ ready to merge

Release Preview — v0.42.0 → v0.42.1

Note: Labels on this PR are advisory in standing-pr mode. Bumps come from conventional commits in the standing PR; override by editing labels on the standing PR itself. Add release:immediate to bypass the standing PR and release this PR directly.

These changes will be added to the release PR (#730) when merged:

Changelog

monorepo 0.42.0 → 0.42.1

Changed

• move the setupGit ref seeds away from #729's status seed (release)
• list every job in the standing-PR secrets table (ci)
• pass LLM provider keys on immediate releases (ci)

Fixed

• fall back to the event's head commit for the delete lease (release)
• match the standing branch exactly, and harden the lease checks (ci)
• keep immediate-release off the standing PR, and tidy hints (ci)
• refuse a push lease whose expect isn't a commit SHA (git)
• keep immediate releases queued with updates (ci)
• lease the branch delete on the merged PR's head (release)
• stop closed-PR events cancelling or replacing a publish (ci)
• delete the release branch under a lease (release)
• give closed-PR runs a group per PR so a queued publish isn't replaced (ci)
• guard release branch delete against concurrent updates (release)
• standing-PR templates — publish concurrency, LLM on publish, pnpm setup (ci) (#739)

All packages → 0.42.1 (sync versioning)

• @releasekit/version
• @releasekit/notes
• @releasekit/publish
• @releasekit/release

After merge — predicted release

No version escalation — this PR's changes will be included in the queued release without affecting the projected versions.

Package	Standing PR	This PR	After merge
monorepo	0.42.1	0.42.1	0.42.1

---

Updated automatically by ReleaseKit

[goosewobbler]

@greptile review

[goosewobbler]

@greptile review