[goosewobbler]

Summary

Documents the trade-off of Allow GitHub Actions to create and approve pull requests: the same toggle lets any workflow token approve PRs, and that approval counts toward a ≥ 1-approval ruleset.

• ci-setup.md has a new "Workflow token approvals" section under "Securing the standing PR". It explains the risk, including the release:immediate path, and what to add to ruleset 2:
  • Require review from Code Owners, with a CODEOWNERS * rule naming an owner with write access, and no later pattern without one.
  • Dismiss stale pull request approvals when new commits are pushed.
  • It notes that each standing-PR update can dismiss the standing PR's approval, so approve it just before merging.
• It says none of this applies to bypass actors, so a bypass given to the Actions bot is open to every workflow. The template's immediate-release job needs one on main, so remove it if you rely on the settings above (tracked in Standing-PR setup: bypasses for the Actions bot and workflow-wide id-token: write reach every workflow #785).
• It recommends publishing from an environment restricted to the default branch, with registry tokens as environment secrets and the environment required by each trusted publisher. A merged PR's closed run has the branch it merged into as its ref, so the merge-triggered publish jobs pass. A label-triggered retry may not.
• Ruleset 1's lock, docs/agents.md and docs/troubleshooting.md now say what an Actions-bot bypass opens up.
• The setup requirement and ruleset 2 link to the section. So do the standing-PR template, examples/ci/standing-pr/standing-pr.yml and its README, the migration guide's setup step and docs/agents.md.

#653 also proposed a GitHub App token with the toggle off, which this PR leaves out on purpose. The App's key would be a repository secret, which any workflow on any branch can read, so a collaborator's workflow could mint an App token and approve their own PR. That's the same gap.

Fixes #653

Made with Cursor

Confidence Score: 5/5

The PR appears safe to merge; the previous publishing-environment omission is fixed.

Summary

Documents the approval risk of GitHub Actions’ create-and-approve toggle.

• Standing-release setup guidance now warns that the Actions toggle enables approvals.
• Publishing guidance shows how both release jobs can use a restricted environment.

_{Reviews (4) · Last reviewed commit: "docs(ci): require the publish environmen..." · Reviewed by Greptile}

[github-actions]

Standing release PR: #730 · v0.42.1 queued (4 packages) · open 7h 37m · ✅ 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

• restore the default-branch environment advice (ci)
• cover bypasses, stale approvals and CODEOWNERS gaps (ci)
• say that publishOrder turns off the crate dependency sort (rust) (PR #787)
• correct the workflow token approval guidance (ci)
• say once where the publish environment goes (ci)
• move the template's approval note below the guide link (ci)
• cover retry-publish and refresh-after-release in the approval guidance (ci)
• require the publish environment on immediate releases too (ci)
• environment protection requires environment secrets (ci)
• warn that the Actions PR toggle also grants approvals (ci)

Fixed

• keep dependency order and branch-first push in per-package mode (publish) (PR #765)

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

[goosewobbler]

@greptile review

[goosewobbler]

@greptile review