chore(deps): update pnpm/action-setup action to v6#977
Conversation
Deploying control-layer with
|
| Latest commit: |
b864846
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://24bb055e.control-layer.pages.dev |
| Branch Preview URL: | https://renovate-pnpm-action-setup-6.control-layer.pages.dev |
renovate
Bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
21 times, most recently
from
ceee79c to
628e91f
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
8 times, most recently
from
cd46ecd to
f30f8f7
Compare
![doubleword-code[bot]](https://avatars.githubusercontent.com/in/3610877?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 change is part of Renovate's automated dependency management.
Verdict: Approved - This is a safe, routine dependency update with no breaking changes affecting the current usage pattern.
Research notes
Fetched the pnpm/action-setup repository and release notes:
- v6.0.0 (April 2025): Added support for pnpm v11. No breaking changes for users who explicitly specify a
versioninput. - v6.0.1-v6.0.8: Bug fix releases including Windows path fixes, cache handling improvements, and pnpm version updates.
- v5.0.0: Updated to Node.js 24 (internal implementation detail).
The workflows use version: 10 explicitly, which remains fully supported in v6. The action's README confirms this usage pattern is valid for both explicit version installation and packageManager field-based installation.
Suggested next steps
- Merge as-is - No changes required. The update is backward compatible and follows the documented usage pattern.
- Consider monitoring the
packageManagerfield indashboard/package.jsonif the project plans to upgrade to pnpm v11 in the future.
General findings
None - the change is minimal and correctly implemented across all three locations.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three locations in two workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). This is a routine dependency update performed by Renovate.
Verdict: Ready to approve — this is a low-risk maintenance update with no breaking changes for the current configuration.
Research notes
Fetched the pnpm/action-setup repository and releases page:
- v6.0.0 (April 2025): Added support for pnpm v11
- v6.0.1-v6.0.8: Bug fixes including:
- Fixed pnpm self-update binary shadowing on PATH
- Fixed npm co-location with action node binary
- Fixed bin_dest output pointing to self-updated pnpm
- Honor devEngines.packageManager.onFail=error
- Updated bundled pnpm to 11.1.1
- Windows standalone + self-update fixes
The workflows currently specify version: 10 for pnpm, which is fully compatible with action v6 (the action supports installing any pnpm version regardless of the action's major version).
Suggested next steps
- Merge as-is — this is a straightforward dependency update with no code changes required.
- Consider enabling Dependabot/Renovate auto-merge for similar low-risk action updates in the future.
General findings
No issues found. All three references to pnpm/action-setup have been consistently updated from v5 to v6. The other workflow files (build-staging.yml, release-please.yaml, autolabel.yaml, pr-title-check.yml) do not use this action and require no changes.
There was a problem hiding this comment.
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). This is a routine dependency upgrade maintained by Renovate bot.
Verdict: Approved — The change is straightforward, low-risk, and aligns with the project's existing practice of keeping GitHub Actions current (the workflows already use actions/checkout@v6 and actions/setup-node@v6).
Research notes
- Fetched the pnpm/action-setup repository: v6 is the current stable version (latest release v6.0.8, May 2026)
- The action's input schema remains compatible — all three usages correctly specify
version: 10to install pnpm 10 - No breaking changes affect the configuration used in these workflows
Suggested next steps
- Merge this PR after confirming CI passes — no code changes required.
General findings
None — the changes are correct and complete.
There was a problem hiding this comment.
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 affects three locations total, all using identical configuration (version: 10).
Verdict: Ready to approve — this is a standard, low-risk dependency update.
Research notes
Fetched the pnpm/action-setup repository page and releases page:
- v6.0.0 (April 10, 2025): Added support for pnpm v11. This is compatible with the workflows' pinned
version: 10. - v6.0.8 (latest, May 12, 2026): Bug fixes for Windows standalone mode, documentation corrections, and pnpm 11.1.1 update (not used here since version is pinned to 10).
- v5.0.0: Updated to Node.js 24, which aligns with the workflows'
node-version: "24".
No breaking changes affect the simple usage pattern in these workflows (explicit version input without advanced options like run_install, cache, or standalone).
Suggested next steps
- Approve and merge — no changes required. This is a routine maintenance update.
General findings
None. The change is minimal, well-scoped, and follows the repository's existing patterns for GitHub Actions version management.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in three locations across two workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml).
Verdict: Approved - This is a safe, routine dependency update.
Research notes
Fetched the pnpm/action-setup repository and releases page:
- v6.0.0 (April 2025): Added support for pnpm v11. No breaking changes to the action's API or inputs.
- v6.0.1–v6.0.8: Bug fixes including Windows standalone mode fixes, PATH handling improvements, and documentation corrections.
- v5.0.0: Updated the action to use Node.js 24 (which matches this project's
actions/setup-node@v6withnode-version: "24").
The workflows explicitly specify version: 10 for pnpm, which remains fully supported by v6 of the action. The major version bump reflects pnpm v11 compatibility, not breaking changes to how the action is invoked.
Suggested next steps
- Merge as-is — this is a straightforward dependency update with no code changes required.
- Consider consolidating the pnpm version specification if the project plans to upgrade to pnpm v11 in the future (not part of this PR).
General findings
No issues found. The change is minimal, well-scoped, and follows the project's existing patterns for GitHub Actions versioning (using major version tags like @v6). All three updated locations are consistent.
There was a problem hiding this comment.
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). This is a routine dependency update managed by Renovate.
Verdict: Approved - The change is safe and follows best practices for GitHub Actions version management.
Research notes
From the pnpm/action-setup releases:
- v6.0.0 (April 2025): Added support for pnpm v11, maintaining backward compatibility with earlier versions
- v6.0.x patch releases: Bug fixes for Windows standalone mode, cache handling, and self-update mechanics
- The workflows explicitly specify
version: 10, which remains fully supported by v6
The README confirms the input schema is unchanged for this usage pattern.
Suggested next steps
- Merge this PR as-is - no changes required
- Consider whether you want to upgrade to pnpm v11 in a future PR (update
version: 10toversion: 11or use thepackageManagerfield frompackage.json)
General findings
None - this is a clean, low-risk dependency update with no identified issues.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml and release.yml). The v6 release primarily adds support for pnpm v11 while maintaining backward compatibility with pnpm v10 (which is explicitly specified in all workflows via version: 10).
Verdict: Ready to approve — this is a low-risk, routine dependency update.
Research notes
- Fetched pnpm/action-setup repository — v6.0.0 was released on Apr 10, 2026 by Zoltan Kochan (pnpm author)
- Release notes indicate v6.0.0 "Added support for pnpm v11" — no breaking changes mentioned for existing v5 users
- The action README confirms the API surface (inputs:
version,cache,run_install, etc.) remains stable between v5 and v6 - All three workflow usages explicitly pin
version: 10, so they will continue using pnpm v10 regardless of the action version bump
Suggested next steps
- Merge as-is if CI passes — this is a standard minor version bump for a well-maintained action.
- Consider enabling Renovate's group updates if not already configured, to batch similar action updates together.
General findings
None. The change is minimal, consistent across all occurrences, and follows GitHub Actions best practices (pinning major versions). No security concerns, no functional regressions expected.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml and release.yml). The change affects two jobs in the CI workflow (frontend-test and e2e-test-docker) and one job in the release workflow (publish-crates).
Verdict: Ready to approve. This is a routine dependency update with no breaking changes for the current usage pattern.
Research notes
From the pnpm/action-setup repository:
- v6.0.0 (April 10, 2026): Added support for pnpm v11. The workflows already specify
version: 10, so this major version bump of the action itself doesn't change the pnpm version being installed. - Latest release v6.0.9 (June 15, 2026): Updates bundled pnpm to v11.7.0, but again this doesn't affect the repo since
version: 10is explicitly pinned. - The README confirms backward compatibility when an explicit
versioninput is provided. - No breaking API changes between v5 and v6 for the inputs currently used (
versionandwith.version).
The workflows use:
uses: pnpm/action-setup@v6
with:
version: 10This pattern remains fully supported in v6.
Suggested next steps
- Merge this PR — it's a safe, routine dependency update.
- Consider whether pnpm v11 should be adopted separately (currently pinned to v10).
General findings
No issues found. The change is minimal, well-scoped, and follows established patterns in the codebase. All three occurrences of pnpm/action-setup@v5 are updated consistently to v6.
There was a problem hiding this comment.
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). This is a routine dependency maintenance update performed by Renovate.
Verdict: Ready to approve — this is a safe, non-breaking update.
Research notes
I fetched the pnpm/action-setup repository page and releases page to understand what changed between v5 and v6:
- v6.0.0 (April 10, 2025): "Added support for pnpm v11" — this is the main major version change
- Subsequent patch releases (v6.0.1 through v6.0.9) include bug fixes such as:
- Fixed pnpm self-update binary shadowing issues
- PATH handling improvements for npm bootstrap
- Windows compatibility fixes
- Updated default pnpm versions
The workflows explicitly specify version: 10 in the action inputs, meaning they will install pnpm 10.x regardless of the action's major version. There is no packageManager field in the project's package.json, so the action does not auto-detect a version.
Suggested next steps
- Approve and merge — this is a standard, low-risk dependency update that keeps the CI infrastructure current.
General findings
No issues found. The change is minimal, well-scoped, and follows best practices for GitHub Actions version management. The explicit version: 10 pin provides a safety net ensuring consistent behavior regardless of the action's major version.
There was a problem hiding this comment.
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 straightforward dependency maintenance update.
Verdict: Ready to approve.
Research notes
I reviewed the pnpm/action-setup repository and release notes:
- v6.0.0 (April 2026): Added support for pnpm v11
- v6.0.9 (latest, June 2026): Bug fixes including Windows standalone mode, pnpm v11.7.0 update, cache handling improvements, and binary path resolution fixes
The workflows currently specify version: 10, which remains fully compatible with action v6. No breaking changes affect the current usage pattern.
Suggested next steps
- Approve and merge — This is a safe, routine update that keeps the CI infrastructure current.
General findings
None. The changes are minimal, well-scoped, and consistent with the other action versions used in these workflows (e.g., actions/checkout@v6, actions/setup-node@v6).
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in three locations across two workflow files. Based on the release notes, v6 primarily adds support for pnpm v11. Since all usages in these workflows explicitly pin version: 10, the change is non-breaking for this codebase.
Verdict: Ready to approve - this is a routine dependency maintenance update with no identified risks.
Research notes
- Fetched pnpm/action-setup README - confirms v6 maintains backward-compatible API with inputs
version,cache,run_install, etc. - Fetched releases page - v6.0.0 released April 10, 2026 with primary change being pnpm v11 support; subsequent patches (through v6.0.9 as of June 15, 2026) fix edge cases around PATH handling, self-update, and Windows compatibility
- No security advisories or known issues found for v6.x
Suggested next steps
No action required - this PR can be merged as-is.
General findings
None - the change is minimal and well-scoped.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three locations in CI/CD workflows. The change is straightforward and low-risk.
Verdict: ✅ Approve - Safe dependency update with no breaking changes expected.
Research notes
Fetched the pnpm/action-setup repository page and releases page:
- v6.0.0 (April 10, 2026): "Added support for pnpm v11"
- The v6 line includes bug fixes for Windows self-update, PATH handling, and bootstrap behavior
- Latest v6.0.9 bundles pnpm v11.7.0
Key finding: All three usages in this PR explicitly specify version: 10, meaning:
- The workflows will continue installing pnpm 10.x (not 11.x)
- The action version primarily controls which pnpm versions can be installed, not what must be installed
- When
versioninput is provided, it overrides the action's default behavior per the README
Suggested next steps
No action required. This PR can be merged as-is. The explicit version: 10 parameter ensures the upgrade doesn't inadvertently change the pnpm version being used.
General findings
None. This is a clean, routine dependency update typical of Renovate bot contributions. The change maintains consistency across both workflow files (ci.yaml and release.yml) and aligns with the project's existing pattern of keeping GitHub Actions up to date (e.g., actions/checkout@v6, actions/setup-node@v6).
There was a problem hiding this comment.
Summary
This PR updates pnpm/action-setup from v5 to v6 across three GitHub Actions workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). The change is part of routine dependency maintenance via Renovate.
Verdict: Ready to approve - this is a low-risk, straightforward dependency update.
Research notes
- v6.0.0 release notes: "Added support for pnpm v11" with no breaking changes documented (release notes)
- Current usage: All workflows explicitly specify
version: 10, which remains fully compatible with action v6 - Latest version: v6.0.9 (June 15, 2026) - actively maintained
- Consistency: Other actions in these workflows already use v6 (
actions/checkout@v6,actions/setup-node@v6,docker/metadata-action@v6)
Suggested next steps
No changes required. This PR can be merged as-is.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three locations in two workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). This is a routine dependency update managed by Renovate.
Verdict: Approved — The change is safe and follows best practices for GitHub Actions version management.
Research notes
- v6.0.0 release notes: Added support for pnpm v11, but remains backward compatible with pnpm v10 when explicitly specified via the
versioninput - Latest v6.0.9 (June 15, 2026): Minor fixes including pnpm version updates to v11.7.0
- Action documentation: Confirms that v6 supports the npm versioning scheme for the
versioninput, including exact versions like10 - The workflows specify
version: 10, which continues to work correctly with action v6
Suggested next steps
No changes required. This PR can be merged as-is.
General findings
None. All three occurrences of pnpm/action-setup have been updated consistently, and the explicit version: 10 parameter ensures compatibility regardless of the action's default behavior.
There was a problem hiding this comment.
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). This is a routine dependency maintenance update.
Verdict: Approved — no blocking issues identified.
Research notes
- Fetched the pnpm/action-setup repository and releases page
- v6.0.0 (April 10, 2026): Primary change was adding support for pnpm v11
- Current latest version is v6.0.9 (June 15, 2026)
- All commits are GPG-signed and verified
- The workflows in this PR explicitly specify
version: 10, so they will continue using pnpm 10 (not pnpm 11) - v6 maintains backward compatibility with pnpm 10
Suggested next steps
- Merge as-is — this is a low-risk dependency update that keeps the CI/CD pipelines current with the latest stable version of the action.
General findings
None. The change is straightforward and follows best practices for GitHub Actions version management.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in three locations across two workflow files (.github/workflows/ci.yaml and .github/workflows/release.yml). The change is a routine dependency update performed by Renovate.
Verdict: Approved — the update is safe and backward-compatible with the current usage pattern.
Research notes
-
pnpm/action-setup README: The v6 version maintains the same input schema (
version,cache,run_install, etc.) as v5. The usage examples showuses: pnpm/action-setup@v6withversion: 10, which matches exactly how this repository uses the action. -
v6.0.0 release notes: States "Added support for pnpm v11" — this is an additive change, not a breaking one. The action continues to support installing any specified pnpm version via the
versioninput. -
v6.0.9 release notes: Latest patch release updates bundled pnpm to v11.7.0; no breaking changes mentioned.
The repository currently specifies version: 10 in all three usages, which remains fully supported under v6.
Suggested next steps
No action required. This PR can be merged as-is. The update:
- Keeps the action on a maintained major version
- Maintains compatibility with the existing
version: 10configuration - Aligns with other actions already updated to v6 (e.g.,
actions/checkout@v6,actions/setup-node@v6)
General findings
None. The change is minimal, well-scoped, and follows the established pattern of keeping GitHub Actions up to date.
There was a problem hiding this comment.
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 a straightforward version bump with no modifications to how the action is invoked—both continue to specify version: 10 explicitly.
Verdict: Approve — This is a safe, routine dependency update with no breaking changes affecting the current usage pattern.
Research notes
- pnpm/action-setup README confirms v6 maintains the same input schema (
version,cache,run_install, etc.) as v5. The usage examples showuses: pnpm/action-setup@v6withversion: 10as a valid configuration. - Latest release v6.0.9 (June 15, 2026) contains only a fix to update pnpm to v11.7.0 internally—no breaking changes to the action's interface.
- The repository's
dashboard/package.jsondoes NOT include apackageManagerfield, meaning the explicitversion: 10input in the workflows is correctly required and remains compatible with v6.
Suggested next steps
No action required. This PR can be merged as-is.
General findings
None. The change is minimal, well-scoped, and follows the existing pattern for GitHub Actions version management in this repository (e.g., actions/checkout@v6, actions/setup-node@v6).
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across two workflow files (ci.yaml and release.yml). The change is minimal and routine—updating 3 occurrences of the action reference.
Verdict: Approved — This is a safe, low-risk dependency update.
Research notes
From the pnpm/action-setup releases:
- v6.0.0 (April 10, 2026): "Added support for pnpm v11" — the major version bump reflects pnpm v11 compatibility, not breaking changes to the action's API
- Latest: v6.0.9 (June 15, 2026) — includes minor bug fixes like pnpm version updates
- The workflows specify
version: 10explicitly, which remains fully compatible with action v6 - No breaking changes to the action's inputs or outputs between v5 and v6
The README confirms the action maintains backward compatibility with earlier pnpm versions when an explicit version input is provided.
Suggested next steps
- Merge as-is — no changes required.
- Consider enabling Dependabot auto-merge for similar low-risk action updates to reduce PR overhead.
General findings
None. The diff is straightforward:
.github/workflows/ci.yaml: Lines 19 and 352 updated from@v5→@v6.github/workflows/release.yml: Line 100 updated from@v5→@v6
All surrounding context (the with: { version: 10 } block) remains unchanged, ensuring consistent behavior.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across three workflow files (ci.yaml at two locations and release.yml).
Verdict: Approved - This is a routine, low-risk dependency upgrade.
Research notes
From the pnpm/action-setup repository:
- v6.0.0 (April 10, 2026): Added support for pnpm v11, with bug fixes for PATH handling, caching, and self-update behavior
- Latest version is v6.0.9 (June 15, 2026)
- The workflows explicitly specify
version: 10, so they will continue using pnpm v10 regardless of the action version - No breaking changes affect the current usage pattern
Suggested next steps
- Merge this PR - the update is safe and keeps dependencies current
- Optionally consider upgrading to pnpm v11 in the future (the action now supports it)
General findings
No issues found. The change is:
- Consistent across all three workflow locations
- Backward compatible with the existing
version: 10configuration - Following the project's established pattern of pinning major versions of GitHub Actions (aligns with
actions/checkout@v6,actions/setup-node@v6)
There was a problem hiding this comment.
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). The change is straightforward and safe—the workflows explicitly pin version: 10 for pnpm, which remains fully compatible with action v6.
Verdict: Ready to approve. No changes needed.
Research notes
Fetched documentation and release notes from pnpm/action-setup:
- v6.0.0 (April 10, 2026): Primary change was adding support for pnpm v11. No breaking changes for the usage pattern in this repo (
uses: pnpm/action-setup@v6with explicitversion: 10). - v6.0.1–v6.0.9: Incremental bug fixes including:
- Fixed pnpm self-update binary shadowing on PATH
- Windows-specific fixes for standalone + self-update
- Cache dependency path handling improvements
- Updated bundled pnpm to v11.7.0
The project's Dockerfile confirms pnpm@10 is used (RUN npm install -g pnpm@10), and the workflows explicitly specify version: 10, so there are no compatibility concerns.
Suggested next steps
- Merge this PR - This is a low-risk dependency update that keeps the CI/CD tooling current.
General findings
None. The change is minimal, well-scoped, and follows the existing pattern for GitHub Actions versioning in this repository.
There was a problem hiding this comment.
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 a minor version bump for the action that primarily adds support for pnpm v11 while maintaining backward compatibility with pnpm v10 (which is what the workflows currently use).
Verdict: Ready to approve — this is a low-risk maintenance update.
Research notes
I reviewed the pnpm/action-setup repository and release notes:
- v6.0.0 (April 10, 2026): Added support for pnpm v11
- v6.0.9 (June 15, 2026, latest): Updated bundled pnpm to v10.9.8
- The action supports npm versioning schemes for the
versioninput, soversion: 10continues to work correctly - All releases are GPG-signed by the maintainer (Zoltan Kochan)
The workflows explicitly specify version: 10, which remains fully compatible with action v6. The dashboard's package.json does not have a packageManager field, so the explicit version specification is required and correctly configured.
Suggested next steps
- Approve this PR — the update is safe and keeps the CI tooling current.
- Consider pinning to a specific patch version (e.g.,
pnpm/action-setup@v6.0.9) for reproducible builds, though using@v6is acceptable for a CI action where you want automatic minor/patch updates.
General findings
No issues found. The change is consistent across all three usages:
.github/workflows/ci.yaml(lines 19 and 360).github/workflows/release.yml(line 100)
All instances correctly maintain the version: 10 input, ensuring pnpm v10 is installed as before.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 across both CI and release workflows. This is a straightforward dependency maintenance update.
Verdict: Ready to approve — This is a safe, low-risk update with no breaking changes for the current usage pattern.
Research notes
I reviewed the pnpm/action-setup releases:
- v6.0.0 (April 2025): Major version bump to add support for pnpm v11. No breaking changes for users of pnpm v10.
- v6.0.9 (latest, June 2026): Includes bug fixes such as:
- Fixed Windows standalone + self-update compatibility
- Fixed
cache_dependency_pathtype documentation - Fixed honoring
devEngines.packageManager.onFail=error - Fixed binary shadowing issues on PATH
The workflows explicitly specify version: 10, so they will continue using pnpm v10. The v6 action supports both pnpm v10 and v11.
Suggested next steps
- Approve and merge — No changes required. This is a routine dependency update that improves CI reliability through bug fixes.
General findings
None. The change is minimal, well-scoped, and follows established patterns in the repository (other actions like actions/checkout and actions/setup-node are also pinned to latest major versions).
There was a problem hiding this comment.
Summary
This PR updates pnpm/action-setup from v5 to v6 across two workflow files (ci.yaml and release.yml). The change is straightforward and low-risk.
Verdict: Ready to approve — this is a routine dependency update with no breaking changes for the existing usage pattern.
Research notes
I investigated the pnpm/action-setup repository and release history:
- v6.0.0 (April 2026): Added support for pnpm v11 while maintaining backward compatibility with pnpm v10
- v6.0.1+: Fixed an early bug (issue #228) where the action incorrectly modified
pnpm-lock.yamlfiles - Current usage: All three workflow locations explicitly specify
version: 10, so they will continue installing pnpm 10 regardless of the action major version - Latest: v6.0.9 (June 15, 2026) includes various stability fixes
The usage pattern (uses: pnpm/action-setup@v6 with version: 10) matches the documented examples and is fully supported.
Suggested next steps
- Merge this PR — no changes required
- Consider enabling Dependabot/Renovate auto-merge for minor/patch action updates to reduce review overhead for routine dependency maintenance
General findings
No issues identified. The workflows correctly:
- Pin the pnpm version explicitly (
version: 10) - Use compatible Node.js setup (
actions/setup-node@v6with Node 24) - Follow the recommended caching pattern with
cache-dependency-path
Note: The e2e-test-docker job in ci.yaml (line 359) is currently disabled (if: false per the comment on line 344), but updating its pnpm action is still appropriate for when it's re-enabled.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in three workflow files. The upgrade is straightforward and safe—the v6 major version was bumped to add support for pnpm v11, but since all workflows explicitly pin version: 10, behavior remains unchanged.
Verdict: Approved ✅
Research notes
- Fetched pnpm/action-setup README: Confirmed all inputs (
version,cache,cache_dependency_path,run_install, etc.) are unchanged between v5 and v6 - Fetched v6.0.0 release notes: "Added support for pnpm v11" — no breaking changes mentioned
- Verified all three usages in the diff explicitly specify
version: 10, ensuring consistent behavior
Suggested next steps
None required—this is a safe, routine dependency update that can be merged as-is.
General findings
No issues found. The change is minimal, well-scoped, and follows the existing patterns in the codebase.
There was a problem hiding this comment.
Summary
This PR updates pnpm/action-setup from v5 to v6 across three workflow locations. The change is a routine dependency upgrade with no breaking changes for this project's usage pattern.
Verdict: Approved — safe to merge.
Research notes
Reviewed the pnpm/action-setup repository:
- v6.0.0 (Apr 2026): Added support for pnpm v11
- v6.0.1–v6.0.9: Bug fixes for Windows PATH handling, self-update behavior, cache fixes, and pnpm version updates
- Latest: v6.0.9 (Jun 15, 2026)
The workflows explicitly specify version: 10, which remains fully compatible with action-setup v6. The dashboard/pnpm-lock.yaml uses lockfileVersion: '9.0' (pnpm v10 format).
Suggested next steps
- Merge — Low-risk update following security best practices for GitHub Actions.
General findings
None. The change is minimal, well-scoped, and introduces no regressions.
There was a problem hiding this comment.
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 affects 3 locations total, all using identical configuration (version: 10).
Verdict: Ready to approve — this is a routine dependency update with no breaking changes affecting the current usage patterns.
Research notes
Fetched documentation and release notes from pnpm/action-setup:
- v6.0.0 (April 10, 2026): Added support for pnpm v11. No breaking changes for existing usage patterns.
- v6.0.1–v6.0.9: Bug fixes including:
- PATH management improvements for pnpm binary resolution
- Windows compatibility fixes for standalone mode
- Cache dependency path type corrections
- Self-update binary shadowing fixes
The workflows use version: 10 explicitly, which means pnpm v10 will be installed regardless of what version the action itself bundles. The version input remains fully supported in v6.
Suggested next steps
- Merge as-is — this is a safe, low-risk dependency update.
- Consider pinning to a specific patch version (e.g.,
@v6.0.9) instead of the floating@v6tag if reproducible builds are a priority, though using the major version tag is standard practice for GitHub Actions.
General findings
No issues identified. The update is consistent across all three usages, and the action's interface has not changed in ways that affect these workflows.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in two workflow files (three total occurrences). The change is a routine dependency maintenance update with no breaking changes for the current usage pattern.
Verdict: Approved — Safe to merge.
Research Notes
- v6.0.0 release notes: "Added support for pnpm v11" — the major version bump reflects new pnpm version support, not breaking API changes
- Subsequent patches (v6.0.1–v6.0.9): Bug fixes only (Windows standalone mode, PATH handling, cache improvements)
- Current usage: All three instances specify
version: 10, which remains fully compatible with the v6 action - Action API stability: Inputs (
version,cache, etc.) and outputs are unchanged between v5 and v6
Suggested Next Steps
- Merge this PR — no changes required
General Findings
No issues found. This is a straightforward Renovate dependency update that keeps the CI infrastructure current without introducing any risk to the build pipeline.
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in three locations across two workflow files (ci.yaml and release.yml). The change is part of routine dependency maintenance via Renovate.
Verdict: Ready to approve — this is a low-risk, backward-compatible update.
Research notes
Fetched documentation and release notes from pnpm/action-setup repository:
- v6.0.0 (April 10, 2026): Primary change was adding support for pnpm v11 (release notes). The action maintains backward compatibility with pnpm v10, which is what these workflows specify (
version: 10). - v6.0.1–v6.0.9: Subsequent releases contain only bug fixes (PATH handling, self-update binary shadowing, cache fixes, etc.).
- Known issue: Issue #261 reports a v6 regression where the
destinput breaks on Windows paths containing spaces. This does not affect this codebase as the workflows do not use thedestinput. - No deprecation warnings for v5 were found, though upgrading is recommended to stay current with security patches and bug fixes.
Suggested next steps
- Merge as-is — the update is safe and follows standard dependency maintenance practices.
- Consider pinning to a specific minor version (e.g.,
@v6.0) if you want stricter control over when breaking changes could be introduced, though major version pins (@v6) are the GitHub Actions convention.
General findings
None. The change is minimal, well-scoped, and follows the existing pattern used for other action updates (e.g., actions/checkout@v6, actions/setup-node@v6).
There was a problem hiding this comment.
Summary
This PR updates the pnpm/action-setup GitHub Action from v5 to v6 in three workflow locations (ci.yaml and release.yml). The v6 major version primarily adds support for pnpm v11 while maintaining backward compatibility with pnpm v10, which is currently used in this project. No breaking changes affect the current usage pattern.
Verdict: Approved — Safe, routine dependency update.
Research Notes
- pnpm/action-setup v6.0.0 release: "Added support for pnpm v11" — main change is forward compatibility
- Patch releases v6.0.1–v6.0.9 include bug fixes (Windows support, PATH handling, cache behavior)
- Current usage pattern (
version: 10) remains fully supported per the action README - The dashboard's
package.jsonhas nopackageManagerfield, so explicit version specification is correct
Suggested Next Steps
- Merge as-is — no changes required.
This PR contains the following updates:
v5→v6Release Notes
pnpm/action-setup (pnpm/action-setup)
v6.0.9Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6...v6.0.9
v6.0.8Compare Source
What's Changed
cache_dependency_pathtype by @haines in #257New Contributors
Full Changelog: pnpm/action-setup@v6.0.7...v6.0.8
v6.0.7Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.6...v6.0.7
v6.0.6Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6.0.5...v6.0.6
v6.0.5Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5
v6.0.4Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.3...v6.0.4
v6.0.3Compare Source
Updated pnpm to v11.0.0-rc.5
Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3
v6.0.2Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2
v6.0.1Compare Source
Update pnpm to v11.0.0-rc.2.
pnpm-lock.yamlwill not be saved with two documents unless thepackageManageris set viadevEngines.packageManager. Related issue: #228v6.0.0Compare Source
Added support for pnpm v11.
v6Compare Source
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.