build(deps): bump pnpm/action-setup from 5 to 6 - #10241
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
dependabot
Bot
added
ci
dependabot
Bot
added
dependencies
Contributor
Dependency ReviewThe following issues were found:
License Issues.github/workflows/ci-mc-gradle-cache.yml
.github/workflows/python-test-package.yml
.github/workflows/utils-nx-kbve-shell.yml
.github/workflows/utils-update-version-toml.yml
OpenSSF Scorecard
Scanned Files
|
dependabot
Bot
force-pushed
the
dependabot/github_actions/dev/pnpm/action-setup-6
branch
from
April 25, 2026 00:21
db15157 to
9896db1
Compare
dependabot
Bot
force-pushed
the
dependabot/github_actions/dev/pnpm/action-setup-6
branch
2 times, most recently
from
May 8, 2026 03:04
d20d68f to
728a1ff
Compare
Bumps [pnpm/action-setup](https://github.com/pnpm/action-setup) from 5 to 6. - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@v5...v6) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/dev/pnpm/action-setup-6
branch
from
May 11, 2026 07:52
728a1ff to
4b1f981
Compare
h0lybyte
added a commit
that referenced
this pull request
Aug 2, 2026
…ive-webgpu (#15161) Consolidates dependabot PRs #14719, #14720, #14722, #14723, #14725. - prost/prost-build 0.13 -> 0.14 in uniti; aligns with every other crate in the workspace, which was already on 0.14. Regenerates the checked-in proto modules (additive Eq/Hash derives only). - syn 3.0.2 -> 3.0.3 (Cargo.lock). - @nxlv/python 22.2.1 -> 22.2.2. - postcss-merge-rules ^7.0.8 -> ^8.0.1. - react-native-webgpu 0.5.15 -> 0.6.3, bumped in both the root manifest and apps/kbve/kbve-react-native so the app does not resolve a second copy. Peer ranges are unchanged and Canvas/useCanvasRef/useDevice still export from the package root. Not included: expo-dev-client 57 (#14728) requires Expo SDK 57 while the workspace is on Expo 56, and pnpm/action-setup v6 (#10241) which is stale and only covers part of the workflows still on v5/v4.
h0lybyte
added a commit
that referenced
this pull request
Aug 2, 2026
…pace alignment (#15174) * ci: bump pnpm/action-setup to v6 across all workflows Supersedes the stale dependabot PR #10241, which covered 20 workflows and left the rest on v5 and ci-unity.yml on v4. This takes all 29 call sites in 24 workflows at once so there is no v4/v5/v6 split to reason about later. v6 exists to add pnpm v11 support, and the workspace is on pnpm 11.15.0. Every call site pins that version explicitly, so v5 was not visibly broken, but staying on a major that predates the pnpm version we actually run is not worth the ambiguity. The action's input surface is unchanged between v5 and v6 - same version, dest, run_install, cache, cache_dependency_path, package_json_file and standalone inputs, same node24 runtime - so no call site needed edits beyond the ref. All 62 workflow files still parse as YAML. * build(deps): align what can be aligned in the standalone Tauri workspaces chuck-launcher, deathslayer-launcher and desktop-kbve/src-tauri each declare their own [workspace], so cargo cannot bind them to the root [workspace.dependencies] added in #15165. They have to be tracked by hand. Aligned to the root pins: - dirs 5 -> 6 in both launchers. Only dirs::data_local_dir() is used and it is unchanged. This also drops the old dirs-sys 0.4 subtree (redox_users plus a full windows-sys/windows-targets set), so the launcher lock gets smaller. - tokio 1 -> 1.49 and thiserror 2 -> 2.0.12, floor raises only. reqwest is deliberately NOT bumped to 0.13 here, unlike the main workspace. 0.13's rustls feature pulls the aws-lc-rs provider, and these three are separate workspaces with their own lockfiles - so there is no shared-tree to deduplicate and the only benefit would be cosmetic. The cost is real: building the bumped version pulled aws-lc-rs, aws-lc-sys and cmake into the launcher lock, which none of them needed before. ci-tauri-builder.yml runs on macos-latest, windows-latest and a Linux runner with no cmake or NASM setup step, and aws-lc-sys wants both on Windows. Trading a working desktop release pipeline for version-string tidiness is not worth it. Left as-is for the same reason: desktop-kbve keeps reqwest's default features (native-tls), so it was never on the rustls path the main workspace uses. Verified with cargo check --all-targets in each of the three workspaces separately, 0 errors. deathslayer-launcher needs its icons/ generated to build at all - only README.md is tracked there, so tauri::generate_context! fails on unmodified dev too; checked with the icon set temporarily stubbed in. Unrelated observation while here: deathslayer-launcher's Cargo.lock is untracked while chuck-launcher's and desktop-kbve's are committed. Not changed here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps pnpm/action-setup from 5 to 6.
Release notes
Sourced from pnpm/action-setup's releases.
Commits
91ab88efix: bin_dest output points to self-updated pnpm, not bootstrap (#249)e578e19fix: update pnpm to 11.0.48912a91fix: append (not prepend) action node dir to PATH for npm bootstrap (#241)26f6d4ffix: use npm co-located with the action node binary (#239)903f9c1fix: update pnpm to 11.0.0-rc.5bdf0af2test: add strict version-match jobs to reproduce #225 / #22771c9247fix: pnpm self-update binary shadowed by bootstrap on PATH (#230)078e9d4fix: update pnpm to 11.0.0-rc.208c4be7docs(README): update action-setup version5798914chore: update .gitignore