chore(deps): update pnpm/action-setup action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pnpm/action-setup	action	major	v5 → v6

---

Release Notes

pnpm/action-setup (pnpm/action-setup)

v6.0.8

Compare Source

v6.0.7

Compare Source

v6.0.6

Compare Source

What's Changed

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

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

v6.0.5

Compare Source

What's Changed

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

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

v6.0.4

Compare Source

What's Changed

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

New Contributors

• @​benquarmby made their first contribution in #​239

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

v6.0.3

Compare Source

Updated pnpm to v11.0.0-rc.5

Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3

v6.0.2

Compare Source

What's Changed

• fix: pnpm self-update binary shadowed by bootstrap on PATH by @​oniani1 in #​230

New Contributors

• @​oniani1 made their first contribution in #​230

Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2

v6.0.1

Compare Source

Update pnpm to v11.0.0-rc.2. pnpm-lock.yaml will not be saved with two documents unless the packageManager is set via devEngines.packageManager. Related issue: #​228

v6.0.0

Compare Source

v6

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying control-layer with    Cloudflare Pages

Latest commit:	25fbbce
Status:	✅  Deploy successful!
Preview URL:	https://0d77ce25.control-layer.pages.dev
Branch Preview URL:	https://renovate-pnpm-action-setup-6.control-layer.pages.dev

View logs

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml and release.yml). This is a routine dependency maintenance update.

Verdict: Ready to approve — this is a safe, backwards-compatible update.

Research notes

I reviewed the pnpm/action-setup releases:

• v6.0.0 (April 10, 2025): Added support for pnpm v11. No breaking changes affecting the current usage pattern.
• v6.0.1–v6.0.8: Incremental bug fixes including:
  • Fixed binary shadowing issues on PATH after pnpm self-update
  • Windows-specific fixes for standalone mode
  • Cache handling improvements
  • Documentation fixes for cache_dependency_path

The workflows currently use version: 10 for pnpm, which remains fully compatible with action v6.

Suggested next steps

1. Merge this PR — no changes required.
2. Consider pinning to a specific patch version (e.g., @v6.0.8) instead of @v6 if you want to ensure reproducible CI builds, though the current major-version-only approach is acceptable for a non-critical utility action.

General findings

No issues found. The update is consistent across all three usages:

• .github/workflows/ci.yaml: frontend-test job (line 19)
• .github/workflows/ci.yaml: e2e-test-docker job (line 348)
• .github/workflows/release.yml: publish-crates job (line 100)

All instances correctly maintain the version: 10 input, which specifies pnpm 10.x regardless of the action version.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml and release.yml). This is a routine dependency maintenance update generated by Renovate.

Verdict: Ready to approve - this is a low-risk, beneficial update.

Research notes

I reviewed the pnpm/action-setup repository and release notes:

• v6.0.0 (April 2025): Added support for pnpm v11. The workflows in this PR continue to use version: 10, which remains fully compatible.
• v5.0.0: Updated the action to use Node.js 24.
• v6.0.1-v6.0.8: Bug fixes including:
  • Fixed pnpm self-update binary shadowing on PATH
  • Fixed standalone + self-update on Windows
  • Cache key improvements
  • Honor devEngines.packageManager.onFail=error

The latest release is v6.0.8 (May 12, 2026).

Suggested next steps

1. Merge this PR - The update is safe and brings bug fixes from the v6.x series.
2. Consider enabling auto-merge for similar Renovate dependency updates to reduce review overhead.

General findings

No issues found. The change is correctly applied to all three usages of pnpm/action-setup in the codebase:

• .github/workflows/ci.yaml: Lines 19 and 348 (frontend-test and e2e-test-docker jobs)
• .github/workflows/release.yml: Line 100 (publish-crates job)

All workflows correctly pin version: 10 for pnpm itself, ensuring consistent behavior regardless of the action version.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml and release.yml). This is a routine Renovate dependency update.

Verdict: Approved — safe to merge.

Research notes

I reviewed the pnpm/action-setup repository and release notes:

• v6.0.0 (April 2025): Added support for pnpm v11. No breaking changes for existing usage patterns.
• v6.0.1-v6.0.8: Bug fixes including Windows standalone mode fixes, cache handling improvements, and pnpm version updates.
• v5.0.0: Updated the action to use Node.js 24 (same as what this repo currently uses).

The workflows in this PR specify version: 10 (pnpm 10), which remains fully compatible with action v6. The action is used in a basic setup pattern without advanced features like run_install, standalone, or custom cache paths.

Suggested next steps

1. Merge this PR — it's a straightforward, low-risk dependency update.
2. Consider whether the project wants to upgrade to pnpm 11 in a future update (not required by this PR).

General findings

None. The change is minimal, well-scoped, and follows the existing patterns in the codebase. All three occurrences are consistent and correctly updated.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). The upgrade is straightforward with no breaking changes—v6.0.0 primarily adds support for pnpm v11, while the existing workflows continue using pnpm v10 which remains fully compatible.

Verdict: Ready to approve—this is a routine maintenance update with no code changes required.

Research notes

• Fetched pnpm/action-setup repository page: Confirmed v6 is the latest stable version (v6.0.8 as of May 12, 2026)
• Fetched v6.0.0 release notes: Release states "Added support for pnpm v11" with no breaking changes mentioned for existing usage patterns
• Current workflow configuration uses version: 10 explicitly, which is within the supported range for v6 of the action

Suggested next steps

1. Approve and merge - This is a safe, non-breaking dependency update that keeps the CI tooling current. No additional changes needed.

General findings

None—the change is minimal, well-scoped, and follows established patterns in the repository. All three instances of pnpm/action-setup are updated consistently.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three locations in the CI and release workflows. The change is straightforward and low-risk.

Verdict: Ready to approve - no blocking issues identified.

The update is compatible with the current configuration (version: 10 for pnpm) and aligns with the existing Node.js 24 setup already in use via actions/setup-node@v6.

Research notes

From the pnpm/action-setup releases page:

• v6.0.0 (April 10, 2025): Added support for pnpm v11. This is the main breaking change that justified the major version bump.
• v5.0.0 (March 17, 2025): Updated the action to use Node.js 24 internally.
• Latest version is v6.0.8 (May 12, 2026) with minor bug fixes for Windows standalone mode and documentation updates.

The workflows currently specify version: 10 for pnpm, which remains fully supported in v6 of the action. The Node.js 24 runtime in v6 matches the actions/setup-node@v6 with node-version: "24" already used in these workflows.

Suggested next steps

1. Approve and merge - This is a routine dependency update with no known compatibility issues.
2. Consider enabling automated testing of the workflows if not already covered by existing CI runs on pull requests.

General findings

No issues found. The change is:

• Backward compatible: pnpm v10 continues to work with action v6
• Consistent: All three occurrences updated uniformly
• Well-scoped: Only touches the action version references, no other workflow logic changed
• Low risk: GitHub Actions are isolated per-run; any issues would be caught by existing CI checks

[doubleword-code]

Summary

This PR upgrades the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml and release.yml). The change is a routine dependency update managed by Renovate.

Verdict: Approved - This is a safe, backward-compatible upgrade.

Research notes

• pnpm/action-setup releases: v6.0.0 (April 2025) added support for pnpm v11. Subsequent patch releases (through v6.0.8 as of May 2026) include bug fixes for Windows standalone mode, PATH handling improvements, and pnpm version updates.
• pnpm/action-setup README: Confirms the usage pattern uses: pnpm/action-setup@v6 with version: 10 is valid and recommended.
• v5 → v6 is a minor major version bump focused on pnpm version compatibility, not breaking API changes. The inputs/outputs remain the same.

Suggested next steps

1. Merge this PR as-is — the upgrade is safe and follows best practices for GitHub Actions versioning.
2. Consider whether the project should also evaluate upgrading to pnpm 11 (the latest supported by v6), though this is optional and outside the scope of this PR.

General findings

No issues found. The change is minimal, well-scoped, and follows the documented migration path. All three workflow files use identical patterns that are verified correct per the upstream documentation.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across two workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). The change is part of routine dependency maintenance.

Verdict: Ready to approve — This is a straightforward, low-risk dependency update with no breaking changes affecting the current workflow configuration.

Research notes

Fetched the pnpm/action-setup repository and release notes:

• v6.0.0 (April 2025): Added support for pnpm v11. This is the main major version bump.
• v6.0.1–v6.0.8: Bug fixes including Windows standalone mode fixes, PATH handling improvements, and pnpm version updates.
• v5.0.0: Updated the action to use Node.js 24 (same as what's currently configured in your workflows).

Your workflows specify version: 10 for pnpm explicitly, so they're not relying on the action's default pnpm version. The workflows also use actions/setup-node@v6 and actions/checkout@v6, which are compatible with this update.

Suggested next steps

1. Merge this PR — No changes required. The update is safe and follows best practices for keeping CI dependencies current.
2. Consider pinning to a specific patch version (e.g., @v6.0.8) if you want reproducible builds, though using @v6 is acceptable for GitHub Actions as it's a stable major version tag.

General findings

No issues found. The change is minimal, well-scoped, and aligns with the project's existing dependency management approach (using major version tags for GitHub Actions). Both workflow files use consistent configurations, and the pnpm version is explicitly pinned to v10, avoiding any surprises from the action's defaults.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow locations (two in ci.yaml, one in release.yml). This is a routine dependency update with no breaking changes for the current usage pattern.

Verdict: Ready to approve — this is a safe, low-risk maintenance update.

Research notes

I reviewed the pnpm/action-setup release notes:

• v6.0.0: Added support for pnpm v11 (major version due to new pnpm major version support)
• v6.0.1-v6.0.8: Bug fixes including:
  • Fixed pnpm self-update binary being shadowed by bootstrap on PATH (#230)
  • Windows compatibility fix for standalone + self-update (#258)
  • PATH handling improvements for npm co-located with action node binary (#239)
  • Honor devEngines.packageManager.onFail=error (#254)
  • Updated bundled pnpm to 11.1.1 (#248)

The workflows explicitly specify version: 10, which remains fully compatible. The workflows also use actions/setup-node@v6 with Node.js 24, which aligns with v6's Node.js 24 runtime requirement (v5 also used Node.js 24).

General findings

No issues found. The change is minimal, well-scoped, and follows the repository's existing patterns for GitHub Actions version management. All three occurrences are updated consistently.

[doubleword-code]

Summary

This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in two workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). According to the release notes, v6.0.0 primarily adds support for pnpm v11, with subsequent patch releases fixing Windows-specific issues and improving self-update behavior. The latest version (v6.0.8) was released on May 12, 2026.

Verdict: Approve - This is a safe, routine dependency update with no breaking changes affecting the current usage pattern.

Research notes

• Fetched pnpm/action-setup repository page - confirmed v6 is the latest major version with active maintenance
• Fetched releases page - reviewed changelog:
  • v6.0.0: Added support for pnpm v11
  • v6.0.1-v6.0.8: Bug fixes for PATH handling, Windows support, self-update behavior
  • v5.0.0: Updated to Node.js 24 (which matches the workflows' node-version: "24")
• The workflows explicitly specify version: 10 for pnpm, which remains compatible with v6 of the action

Suggested next steps

1. Approve and merge - No changes required. This is a straightforward maintenance update.
2. Consider enabling Renovate auto-merge for minor/patch GitHub Actions updates to reduce PR overhead.

General findings

No issues found. The change is:

• Minimal: Only 3 lines changed across 2 files
• Low-risk: Major version bump is for pnpm v11 support; pnpm v10 (used in workflows) remains supported
• Well-maintained: Action has 1.3k stars, active maintenance, and signed commits from the pnpm core team