build(deps): bump pnpm/action-setup from 6 to 6.0.9 in the github-actions group

[dependabot]

Bumps the github-actions group with 1 update: pnpm/action-setup.

Updates pnpm/action-setup from 6 to 6.0.9

Release notes

Sourced from pnpm/action-setup's releases.

v6.0.9

What's Changed

• fix: update pnpm to v11.7.0 by @​zkochan in pnpm/action-setup#267

Full Changelog: pnpm/action-setup@v6...v6.0.9

v6.0.8

What's Changed

• docs(README): fix cache_dependency_path type by @​haines in pnpm/action-setup#257
• fix: drop patchPnpmEnv so standalone+self-update works on Windows by @​zkochan in pnpm/action-setup#258
• fix: update pnpm to 11.1.1 by @​mungodewar in pnpm/action-setup#248

New Contributors

• @​mungodewar made their first contribution in pnpm/action-setup#248

Full Changelog: pnpm/action-setup@v6.0.7...v6.0.8

v6.0.7

What's Changed

• fix: honor devEngines.packageManager.onFail=error (#252) by @​zkochan in pnpm/action-setup#254
• fix: restore inputs from state in post by @​haines in pnpm/action-setup#255
• fix: self-update bootstrap to packageManager-pinned version (#233) by @​zkochan in pnpm/action-setup#256

New Contributors

• @​haines made their first contribution in pnpm/action-setup#255

Full Changelog: pnpm/action-setup@v6.0.6...v6.0.7

v6.0.6

What's Changed

• fix: bin_dest output points to self-updated pnpm, not bootstrap by @​zkochan in pnpm/action-setup#249

Full Changelog: pnpm/action-setup@v6.0.5...v6.0.6

v6.0.5

What's Changed

• fix: append (not prepend) action node dir to PATH for npm bootstrap by @​zkochan in pnpm/action-setup#241

Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5

v6.0.4

What's Changed

• fix: use npm co-located with the action node binary by @​benquarmby in pnpm/action-setup#239

New Contributors

• @​benquarmby made their first contribution in pnpm/action-setup#239

... (truncated)

Commits

• 62bce64 fix: extract pnpm version from packageManager field instead of returning unde...
• 58e6119 feat!: replace bundled pnpm binary with npm + lockfile bootstrap (#212)
• 2e223e0 chore(workflows): adding pr-check.yaml to validate dist folder (#213)
• fc06bc1 feat!: run the action on Node.js 24 (#205)
• b906aff Revert "feat!: run the action on Node.js 24 (#205)"
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 4, 2026, 4:02 PM ET / 20:02 UTC.

ClawSweeper review

What this changes

Updates pnpm/action-setup from the moving v6 tag to v6.0.9 in the CI and release workflows so builds use the newer pnpm bootstrap.

Merge readiness

⚠️ Ready for maintainer review - 5 items remain

Keep open: current main and v0.7.2 still use pnpm/action-setup@v6, so this small update remains necessary. Because the updated third-party action also executes in the release job with write and OIDC permissions, it needs workflow/security-owner approval before merge.

Priority: P3
Reviewed head: 089e186d4e5b3d39e0673bbac44a81a6bf84f785
Owner decision: Required. See Decision needed.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The patch is narrowly scoped and checked, but privileged release-path provenance still needs a code-owner decision.
Proof confidence	🌊 off-meta tidepool	Not applicable: This Dependabot workflow-only update is exempt from contributor runtime-proof requirements; successful PR checks supplement review, while release-route approval remains a human security decision.
Patch quality	🦐 gold shrimp (3/6)	Security review found an item that needs attention.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This Dependabot workflow-only update is exempt from contributor runtime-proof requirements; successful PR checks supplement review, while release-route approval remains a human security decision.
Evidence reviewed	5 items	Current main and latest release retain the old action ref: Current main and the v0.7.2 release both use pnpm/action-setup@v6, so the requested update is not already implemented. PR scope is narrow: The branch changes exactly the two pnpm/action-setup references to v6.0.9, one in ordinary CI and one in release publishing. Release path is privileged: The updated action runs in the tag-triggered release job, which has contents: write and id-token: write before publishing to npm and GitHub.
Findings	None	None.
Security	Needs attention	Review the unpinned action in the privileged release workflow: The v6.0.9 tag executes third-party action code before npm trusted publishing and GitHub release creation; verify the upstream revision or pin a reviewed full commit SHA.

How this fits together

The GitHub workflows prepare pnpm before installing, validating, and packaging the TypeScript CLI. The release workflow then uses that environment to publish the npm package and GitHub release with elevated permissions.

flowchart LR
  A[Pull request or release tag] --> B[CI or release workflow]
  B --> C[pnpm setup action]
  C --> D[Install and validate CLI]
  D --> E[Package or publish release]
  E --> F[npm and GitHub release]

Loading

Decision needed

Question	Recommendation
Should the repository approve pnpm/action-setup v6.0.9 for the OIDC-enabled release job, and should that approval require an immutable action SHA?	Approve a reviewed immutable reference: Verify the official v6.0.9 source and replace both action tags with the reviewed full commit SHA before merging.

Why: This selects externally supplied executable code for a workflow that can publish packages and releases; the repository explicitly routes workflow ownership to its security operations team.

Before merge

• Resolve security concern: Review the unpinned action in the privileged release workflow - The v6.0.9 tag executes third-party action code before npm trusted publishing and GitHub release creation; verify the upstream revision or pin a reviewed full commit SHA.
• Resolve merge risk (P1) - The changed third-party action runs in the tag-triggered release job with contents: write and id-token: write; ordinary pull-request checks do not exercise that publish path.
• Resolve merge risk (P1) - The v6.0.9 tag is not an immutable commit reference, so approval should include upstream provenance review or a reviewed SHA pin.
• Complete next step (P2) - Route the exact head to the declared workflow security owner for provenance and immutable-reference approval; no mechanical repair is safe without that choice.

Findings

• [medium] Review the unpinned action in the privileged release workflow — .github/workflows/release.yml:63

Agent review details

Security

Needs attention: The diff updates an external action in a release workflow that has write and OIDC permissions, so provenance and reference immutability need owner review.

Review metrics

Metric	Value	Why it matters
Workflow surface	2 files changed; 2 replacements	The same external action update reaches normal CI and the elevated release-publishing workflow.

Merge-risk options

Maintainer options:

1. Review and pin the release action (recommended)
   Confirm the upstream v6.0.9 revision and use its reviewed immutable SHA in both workflows before merge.
2. Accept the version tag after security review
   A workflow code owner may explicitly accept the tag-based update after reviewing its provenance and release-job exposure.

Technical review

Best possible solution:

Use a reviewed immutable reference for the v6.0.9 action at both setup sites, then obtain workflow-owner approval for its use in the privileged release route.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a workflow dependency update, not a reported runtime bug. The supplied checks passed, but a real tag-triggered publishing run is intentionally not exercised by pull-request CI.

Is this the best way to solve the issue?

Unclear: the version update is narrow and clean, but the privileged release use makes a provenance review and immutable-reference decision safer than merging the mutable tag unchanged.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against a81435d851e1.

Labels

Label changes:

• add merge-risk: 🚨 security-boundary: The changed action executes in a release job granted npm OIDC and GitHub contents-write capability.
• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This Dependabot workflow-only update is exempt from contributor runtime-proof requirements; successful PR checks supplement review, while release-route approval remains a human security decision.
• remove status: 👀 ready for maintainer look: Current PR status label is status: ⏳ waiting on author.

Label justifications:

• P3: This is a small patch-level dependency-maintenance update with no demonstrated user-facing regression.
• merge-risk: 🚨 security-boundary: The changed action executes in a release job granted npm OIDC and GitHub contents-write capability.
• merge-risk: 🚨 automation: The patch changes the tool that bootstraps pnpm for CI and release automation.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This Dependabot workflow-only update is exempt from contributor runtime-proof requirements; successful PR checks supplement review, while release-route approval remains a human security decision.

Evidence

Security concerns:

• [medium] Review the unpinned action in the privileged release workflow — .github/workflows/release.yml:63
  The v6.0.9 tag executes third-party action code before npm trusted publishing and GitHub release creation; verify the upstream revision or pin a reviewed full commit SHA.
  Confidence: 0.96

What I checked:

• Current main and latest release retain the old action ref: Current main and the v0.7.2 release both use pnpm/action-setup@v6, so the requested update is not already implemented. (.github/workflows/ci.yml:17, 3c2a1a4e2d04)
• PR scope is narrow: The branch changes exactly the two pnpm/action-setup references to v6.0.9, one in ordinary CI and one in release publishing. (.github/workflows/release.yml:63, 089e186d4e5b)
• Release path is privileged: The updated action runs in the tag-triggered release job, which has contents: write and id-token: write before publishing to npm and GitHub. (.github/workflows/release.yml:21, 089e186d4e5b)
• Workflow ownership requires security routing: Repository CODEOWNERS assigns all workflow files to the OpenClaw security operations team. (.github/CODEOWNERS:11, a81435d851e1)
• Current workflow references date to the latest release commit: Blame attributes both existing pnpm action lines to the v0.7.2 release commit by Peter Steinberger, which is contained in the v0.7.2 tag. (.github/workflows/release.yml:63, 3c2a1a4e2d04)

Likely related people:

• openclaw/openclaw-secops: CODEOWNERS assigns the complete .github/workflows surface to this security operations team. (role: declared workflow code owner; confidence: high; files: .github/CODEOWNERS, .github/workflows/ci.yml, .github/workflows/release.yml)
• Peter Steinberger: Current pnpm action lines blame to the v0.7.2 release commit authored by Peter Steinberger. (role: recent workflow contributor; confidence: high; commits: 3c2a1a4e2d04; files: .github/workflows/ci.yml, .github/workflows/release.yml)
• Vincent Koc: Workflow history associates the release and security automation introduction with this contributor. (role: release automation contributor; confidence: medium; commits: 637d2bd1cf81; files: .github/workflows/release.yml)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Have a workflow code owner verify the v6.0.9 source and approve or request an immutable SHA pin.

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (5 earlier review cycles)

• reviewed 2026-08-03T16:13:21.562Z sha 089e186 :: needs maintainer review before merge. :: none
• reviewed 2026-08-04T05:11:33.308Z sha 089e186 :: needs maintainer review before merge. :: none
• reviewed 2026-08-04T07:12:46.603Z sha 089e186 :: needs maintainer review before merge. :: none
• reviewed 2026-08-04T12:01:32.900Z sha 089e186 :: needs maintainer review before merge. :: none
• reviewed 2026-08-04T17:17:55.807Z sha 089e186 :: needs maintainer review before merge. :: none