chore(deps-dev): bump prisma from 6.19.3 to 7.9.1 - #263
Conversation
Bumps [prisma](https://github.com/prisma/prisma/tree/HEAD/packages/cli) from 6.19.3 to 7.9.1. - [Release notes](https://github.com/prisma/prisma/releases) - [Commits](https://github.com/prisma/prisma/commits/7.9.1/packages/cli) --- updated-dependencies: - dependency-name: prisma dependency-version: 7.9.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Not a bump — Prisma 7 moves the connection URL out of Scoped in #268. The security reason to want it — |
|
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. |
…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.
Bumps prisma from 6.19.3 to 7.9.1.
Release notes
Sourced from prisma's releases.
... (truncated)
Commits
3f492abchore(deps): update@prisma/devto 0.24.17 (7.9.x backport) (#29795)537583cfeat(cli): add@bomb.sh/tabcompletions (#28351)bf7c40ffix(cli): update Studio to 0.33.0 and suppress aborted response errors (#29720)9acd8dcfeat(cli): install Prisma agent skills during prisma init (#29689)aef8cb5fix(cli): remove the migrate-reset tool from the MCP server (#29691)cdca333chore(deps): update@prisma/devto 0.24.14 (#29686)fda8fbcchore(deps): bump@prisma/devto 0.24.9 (resolves hono GHSA-92pp-h63x-v22m) (...5723406fix(cli): route bootstrap telemetry to Prisma Web Properties project (#29473)8e71aa7fix(cli): install missing@prisma/clientinprisma bootstrap(#29444)ada077bfix(cli): bootstrap UX — auto-install deps, resumable flow, timeout handling ...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)