chore(deps): bump pnpm/action-setup from 4 to 6 - #258
Closed
dependabot[bot] wants to merge 2 commits into
Closed
Conversation
Bumps [pnpm/action-setup](https://github.com/pnpm/action-setup) from 4 to 6. - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@v4...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
added
dependencies
dependabot
Bot
added
dependencies
AKogut
added a commit
that referenced
this pull request
Aug 18, 2026
…266) `pnpm audit --prod --audit-level high` currently fails on `main`. That is worth stating plainly first, because it also explains something that looked like noise: the audit check is red on almost every open dependabot pull request, **including #258, which bumps `pnpm/action-setup`** — a GitHub Action that cannot affect a dependency tree at all. The branches were not broken. The base was. ## The three | Package | Found | Fixed in | Arrives through | | --- | --- | --- | --- | | `js-yaml` | 3.15.0 | ≥3.15.1 | `@istanbuljs/load-nyc-config`, via jest's coverage chain | | `nanoid` | 3.3.16 | ≥3.3.18 | `postcss` — whose existing override had drifted behind its own advisory | | `deepmerge-ts` | 7.1.5 | ≥8.0.0 | `@prisma/config`, and Prisma 7 is the only release carrying the fixed one | None is reachable by a direct bump, which is what the comment in `audit.yml` already anticipated: *"advisories reachable through a transitive pin that only a resolution override can clear."* ## Why the overrides are scoped `js-yaml` also ships a 4.x line. A bare `"js-yaml": "^3.15.1"` override would drag every 4.x consumer backwards to fix a 3.x problem — so it is pinned under the one parent that pulls the vulnerable copy. Same reasoning for `deepmerge-ts`: version 8 is wanted under Prisma, not everywhere. `postcss` was already overridden; that entry had simply fallen behind. Raising it also cleared `nanoid`, since that is where it came from. ## The part I did not assume Forcing a **major** of `deepmerge-ts` underneath Prisma 6 is exactly the kind of change that type-checks and then falls over at runtime, so it was run rather than reasoned about: the full suite against a live Postgres, every database-backed test included. ``` Tasks: 28 successful, 28 total ``` Plus build, typecheck and lint: 47/47. ## Result Five findings become one: ``` before 1 low | 1 moderate | 3 high after 1 low ``` The remainder is an esbuild development-server file-read on Windows — below the `--audit-level high` gate the workflow enforces, and reported by the second, non-failing audit step that already exists for exactly this. ## What this unblocks #261 (zod 4) and #263 (prisma 7) fail on their own merits and still need work. The rest — #258, #262, #264, #265 — were failing only on this, and should go green on a rebase.
Owner
|
Superseded by the branch above. This one could not be updated onto the fixed main — the API refuses |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/pnpm/action-setup-6
branch
August 18, 2026 08:18
AKogut
added a commit
that referenced
this pull request
Aug 18, 2026
Replaces #258, which could not be brought up to date: `gh pr update-branch` is refused for any branch touching `.github/workflows`, because the token has no `workflow` scope. ``` GraphQL: refusing to allow an OAuth App to create or update workflow `.github/workflows/ci.yml` without `workflow` scope ``` Applied by hand and pushed over SSH, which is not subject to that scope. All seven workflows that use the action move together — `ci`, `audit`, `docs`, `e2e`, `python`, `release` and `reporters` — rather than leaving some on v4. The real proof for this one is CI running at all: if v6 broke the pnpm setup, nothing below would report.
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
1 participant
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 4 to 6.
Release notes
Sourced from pnpm/action-setup's releases.
Commits
0977fd9docs: Update README to include devEngines.packageManager (#273)48261acfix: update pnpm to v11.19.0 (#283)75677f7ci: use pnpm 11 forpr-check(#284)769ae71refactor: introduce restore keys for cache (#280)6fed91fdocs(README): point users to the successor pnpm/setup action (#282)0ebf471fix: update pnpm to v11.7.0 (#267)0e279bbfix: update pnpm to 11.1.1 (#248)3e83581fix: drop patchPnpmEnv so standalone+self-update works on Windows (#258)551b42edocs(README): fixcache_dependency_pathtype (#257)739bfe4fix: self-update bootstrap to packageManager-pinned version (#233) (#256)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)