feat(cli): show Prisma CLI path in version output by SadmanPinon · Pull Request #29573 · prisma/orm

SadmanPinon · 2026-05-21T05:22:14Z

Summary

Add the Prisma CLI package path to prisma -v / prisma version output.
Resolve the path from the CLI package.json so the output points at the installation responsible for the running CLI.
Update the version command snapshot sanitization for the new path row.

Demo / Review Proof

Short demo video: https://github.com/SadmanPinon/bounty-proof-assets/blob/main/demos/prisma-7771-demo.mp4

Validation

corepack pnpm --filter "prisma..." build
corepack pnpm --filter prisma build
corepack pnpm --filter prisma test src/tests/commands/Version.test.ts
corepack pnpm exec eslint packages/cli/src/Version.ts packages/cli/src/tests/commands/Version.test.ts
corepack pnpm exec prettier --check packages/cli/src/Version.ts packages/cli/src/tests/commands/Version.test.ts
node packages/cli/build/index.js -v

Note: local Node was v23.7.0, so pnpm printed the repo engine warning (^20.19 || ^22.12 || >=24.0), but the build and targeted test passed.

coderabbitai · 2026-05-21T05:22:31Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 18b7e9d5-5e9d-4803-b643-4a325a2f24c4

📥 Commits

Reviewing files that changed from the base of the PR and between 0f34153 and 0300afe.

📒 Files selected for processing (1)

packages/cli/src/__tests__/commands/Version.test.ts

Summary by CodeRabbit

Release Notes

New Features
- The CLI version command now displays the Prisma CLI Path, showing the installation location of the Prisma CLI package alongside other version information.

Walkthrough

The PR extends the Prisma CLI version command to include the local CLI package filesystem path in its output. It resolves the package.json location at runtime, derives the directory path, and adds a "Prisma CLI Path" row to the version output table. Tests and snapshot sanitization were updated to account for the new output row.

Changes

Prisma CLI Path Version Output

Layer / File(s)	Summary
Version command path output implementation `packages/cli/src/Version.ts`	`node:path` module is imported. The Prisma CLI package path is computed from `require.resolve('../package.json')` using `dirname()` and inserted as a new "Prisma CLI Path" row in the version output table.
Test snapshot and sanitization `packages/cli/src/__tests__/commands/Version.test.ts`	The version command test snapshot is updated to reflect the new Studio and Prisma CLI Path output rows. The `cleanSnapshot` helper is extended to sanitize the Prisma CLI Path value to `sanitized_path` for consistent test snapshots.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat(cli): show Prisma CLI path in version output' clearly and specifically summarizes the main change in the PR.
Description check	✅ Passed	The description is directly related to the changeset, detailing implementation of CLI path display, path resolution strategy, and test updates.
Linked Issues check	✅ Passed	The PR fully implements the requirements from issue `#7771`: shows Prisma CLI path in version output using package.json resolution, working across different invocation methods.
Out of Scope Changes check	✅ Passed	All changes are scoped to implementing the feature: modifications to Version.ts for path display and corresponding test snapshot updates are directly aligned with issue `#7771`.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

✨ Simplify code

Create PR with simplified code

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

CLAassistant · 2026-05-21T06:27:53Z

All committers have signed the CLA.

tensordreams · 2026-06-04T08:19:15Z

Thanks — this is a clean, minimal implementation: the row resolution mirrors the existing require('../package.json') pattern, and the snapshot + sanitizer updates in Version.test.ts are correct.

Two asks:

Please sign the CLA (link in the thread above) — it's required before we can merge.
Optional, but it would round this out: a --json assertion on the slugified prisma-cli-path key so both output modes are covered.

We're triaging a large number of overlapping PRs for this issue. If we don't hear back within the next few days, we'll close this PR to keep the queue manageable.

SadmanPinon · 2026-06-08T04:40:17Z

Thanks for the review. The CLA is signed now, and I added coverage for the --json output using the slugified prisma-cli-path key.

Validation run:

corepack pnpm --filter prisma test src/__tests__/commands/Version.test.ts

Result: passed (2 tests, 2 snapshots).

/claim prisma#7771 Fixes prisma#7771 ## Summary - Add the Prisma CLI package path to `prisma -v` / `prisma version` output. - Resolve the path from the CLI package.json so the output points at the installation responsible for the running CLI. - Update the version command snapshot sanitization for the new path row. ## Demo / Review Proof - Short demo video: https://github.com/SadmanPinon/bounty-proof-assets/blob/main/demos/prisma-7771-demo.mp4 ## Validation - corepack pnpm --filter "prisma..." build - corepack pnpm --filter prisma build - corepack pnpm --filter prisma test src/__tests__/commands/Version.test.ts - corepack pnpm exec eslint packages/cli/src/Version.ts packages/cli/src/__tests__/commands/Version.test.ts - corepack pnpm exec prettier --check packages/cli/src/Version.ts packages/cli/src/__tests__/commands/Version.test.ts - node packages/cli/build/index.js -v Note: local Node was v23.7.0, so pnpm printed the repo engine warning (`^20.19 || ^22.12 || >=24.0`), but the build and targeted test passed. --------- Co-authored-by: Oleksii Orlenko <alex@aqrln.net>

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@prisma/adapter-pg](https://github.com/prisma/prisma) ([source](https://github.com/prisma/prisma/tree/HEAD/packages/adapter-pg)) | imports | minor | [`7.9.1` -> `7.10.0`](https://renovatebot.com/diffs/npm/@prisma%2fadapter-pg/7.9.1/7.10.0) | | [@prisma/client](https://www.prisma.io) ([source](https://github.com/prisma/prisma/tree/HEAD/packages/client)) | imports | minor | [`7.9.1` -> `7.10.0`](https://renovatebot.com/diffs/npm/@prisma%2fclient/7.9.1/7.10.0) | --- ### Release Notes <details> <summary>prisma/prisma (@prisma/adapter-pg)</summary> ### [`v7.10.0`](https://github.com/prisma/orm/releases/tag/7.10.0) [Compare Source](prisma/orm@7.9.1...7.10.0) ##### Prisma ORM 7.10.0 Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters. ##### Highlights ##### Run Prisma 7 alongside Prisma 8 This release introduces `@prisma/prisma7`, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project. Once 7.10.0 is released, a side-by-side installation can use: ```sh npm install --save-dev prisma@8 @prisma/prisma7@7.10.0 npm install @prisma/client@7.10.0 ``` Use `prisma` for the directly installed Prisma 8 CLI and `prisma7` for Prisma 7: ```sh npx prisma --version npx prisma7 --version npx prisma7 generate npx prisma7 migrate dev npx prisma7 db push ``` Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's `prisma.config.*` files: ```ts // prisma7.config.ts import { defineConfig } from '@prisma/prisma7/config' export default defineConfig({ schema: 'prisma/schema.prisma', migrations: { path: 'prisma/migrations', }, }) ``` Without an explicit `--config` option, Prisma 7 searches for: 1. Root-level `prisma7.config.*` files. 2. `.config/prisma7.*` files. 3. Existing `prisma.config.*` files as a backwards-compatible fallback. The supported extensions are `.js`, `.ts`, `.mjs`, `.cjs`, `.mts`, and `.cts`. An explicit config path always takes precedence: ```sh npx prisma7 generate --config ./custom/prisma7.config.ts ``` New projects initialized by the Prisma 7 CLI use `prisma7.config.ts`. Existing projects containing only `prisma.config.*` continue to work without migration or additional warnings. If a `prisma7.config.*` file exists but cannot be loaded, Prisma reports the error rather than silently falling back to another configuration. The `prisma7` identity is carried through CLI help, version output, shell completion, initialization, migration, database, and generation guidance. Stable Prisma concepts such as `schema.prisma`, Prisma Migrate, `@prisma/client`, and `PRISMA_*` environment variables remain unchanged. Together, the separate executable and configuration namespace make it possible to operate Prisma 7 and Prisma 8 side by side without command or config-file collisions. [#29949](prisma/orm#29949), [#29969](prisma/orm#29969), [#29994](prisma/orm#29994), [#30000](prisma/orm#30000), [#30002](prisma/orm#30002), [#30020](prisma/orm#30020) ##### Prisma Studio security hardening Prisma Studio's local HTTP server now: - Binds explicitly to `127.0.0.1` instead of all network interfaces. - Rejects browser requests from origins other than the active `localhost` or `127.0.0.1` Studio URL. - No longer returns wildcard CORS headers. - Applies the same protections across Node.js, Bun, and Deno. This prevents network clients or malicious websites from accessing Studio's database endpoints while Studio is running. [#29890](prisma/orm#29890) ##### Prisma Client - Fixed `P2002` errors from nested writes so `meta.modelName` identifies the model where the unique constraint violation occurred, including models using `@@map` and `@@schema`. [#29628](prisma/orm#29628) - Fixed automatically batched `findUniqueOrThrow()` calls so every missing record rejects with `P2025`; later misses no longer resolve to `undefined`. [#29654](prisma/orm#29654) - Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. [#29771](prisma/orm#29771) - Improved interactive transaction cleanup during `$disconnect()`, including transactions whose driver-level startup is still in progress. [#28768](prisma/orm#28768) - Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections. [#29611](prisma/orm#29611) - Fixed fluent relation queries when relation fields are literally named `select` or `include`. [#29683](prisma/orm#29683) - Fixed handling of `Date` and `Uint8Array` values created in other JavaScript realms, such as iframes, jsdom, and Node.js `vm` contexts. [#29177](prisma/orm#29177) - Invalid `Date` values passed to `$queryRaw` or `$executeRaw` now throw `PrismaClientValidationError` instead of a generic error. [#29718](prisma/orm#29718) - Fixed `moduleFormat` inference for the `prisma-client` generator in TypeScript projects using `module: "node16"` or `"nodenext"`. Generated output now follows the nearest `package.json` `type`, defaulting to CommonJS when absent. [#29712](prisma/orm#29712) - Deserialized `Bytes` values now own standalone `ArrayBuffer`s rather than exposing unrelated contents from Node.js's shared `Buffer` pool. This applies to both regular and raw query results. [#29701](prisma/orm#29701) - Fixed an incorrect logging context in the remote executor, including Accelerate-backed query execution. [#28892](prisma/orm#28892) ##### Client extensions and observability - Result-extension `compute` callbacks now receive the current model name as a typed second argument: ```ts compute(data, modelName) { // ... } ``` The model name is also preserved when multiple extensions compose the same computed field. [#29782](prisma/orm#29782) - Improved OpenTelemetry context for remotely executed queries: - `$on('query')` callbacks run within the matching `db_query` span. - Events from one operation share the same trace. - Error events are recorded as span exceptions. - Log events continue to be emitted when tracing is disabled or their reported span is unavailable. [#28892](prisma/orm#28892) ##### Driver adapters ##### MariaDB - `@prisma/adapter-mariadb` now accepts an existing `mariadb` pool. External pools remain caller-owned unless `disposeExternalPool: true` is supplied. [#27992](prisma/orm#27992) - Fixed pooled connection leaks during commit, rollback, and failed transaction startup. Connections are now returned with `release()` and transaction-specific listeners are removed before reuse. [#29612](prisma/orm#29612) - Added support for bracketed IPv6 addresses in both `mysql://` and `mariadb://` connection strings. [#29026](prisma/orm#29026) - Prevented malformed connection strings from exposing embedded passwords in retained debug output and diagnostic reports. [#27992](prisma/orm#27992) ##### PostgreSQL, Neon, and Prisma Postgres Serverless - PostgreSQL deadlocks using SQLSTATE `40P01` are now reported as `P2034` transaction write conflicts. [#29717](prisma/orm#29717) - PostgreSQL `RESTRICT` violations using SQLSTATE `23001` are now reported as `P2003`, preserving an available field or constraint name. [#29554](prisma/orm#29554) - `@prisma/adapter-pg` now preserves database constraint names when reporting unique constraint violations through `P2002`. [#29587](prisma/orm#29587) - Prisma Postgres Serverless now prefers the named constraint for `P2002`, falling back to parsed field names when no constraint name is available. [#29801](prisma/orm#29801) - Fixed Neon HTTP adapter serialization for typed parameters such as `Bytes` and `DateTime`. [#29747](prisma/orm#29747) ##### SQLite - `@prisma/adapter-better-sqlite3` now converts previously unhandled SQLite result codes into typed database errors instead of exposing raw driver errors. - The complete `SQLITE_BUSY` family is now mapped to socket timeout errors, with numeric extended result codes preserved where available. [#29794](prisma/orm#29794) ##### CLI and Migrate - `prisma generate` can now offer to install Prisma's agent skills. The opt-in prompt: - Is shown at most once per machine. - Is skipped in CI, containers, Git hooks, npm lifecycle scripts, and watch mode. - Is skipped when `--no-hints` is used or Prisma skills are already installed. - Times out after 30 seconds. - Never causes generation to fail if installation is unsuccessful. [#29690](prisma/orm#29690) - A globally installed CLI now warns during `prisma generate` when its version differs from the project's local `prisma` or `@prisma/client`, and recommends running the local CLI. The check is best-effort and does not fail generation. [#29593](prisma/orm#29593) - `prisma version` and `prisma version --json` now include the resolved Prisma CLI package path, making global-versus-local installation issues easier to diagnose. [#29573](prisma/orm#29573) - Empty or generator-only schema files now report `Schema must contain a datasource block` from `db pull`, `db push`, and `migrate dev`, rather than reaching the schema engine and potentially producing inconsistent errors. [#29657](prisma/orm#29657) - CLI commands now tolerate corrupt, unreadable, or unwritable command-state files. Invalid state is reinitialized, writes are atomic, and persistence failures fall back to in-memory state. [#29609](prisma/orm#29609) - Studio now recognizes semicolon-delimited `sqlserver://` connection strings before reporting the existing explicit message that SQL Server is not supported by Studio. [#29623](prisma/orm#29623) - The AI-agent safety checkpoint now also covers interactive `prisma db push` confirmations involving data-loss warnings, rather than only invocations using `--accept-data-loss`. [#29793](prisma/orm#29793) ##### Performance and reliability - Optimized query-plan execution by eagerly evaluating plans with one unconditional database operation and synchronously interpreting the remaining pure plan. Cached plans remain immutable. [#29004](prisma/orm#29004) - Prevented call-stack overflows when rendering very large parameter lists or combining chunked results containing hundreds of thousands of rows. [#29751](prisma/orm#29751) - Reduced ordinary query setup overhead by constructing fluent-relation field maps lazily and in linear time. Non-fluent queries no longer build this map. [#29752](prisma/orm#29752) ##### Dependencies - Updated the transitive `fast-uri` dependency to a patched release addressing production audit advisories affecting versions through `3.1.3`. [#29758](prisma/orm#29758) </details> --- ### 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 becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.oirnoir.dev/OIRNOIR/YouTube-Helper-Server/pulls/41

feat(cli): show Prisma CLI path in version output

0f34153

test(cli): cover Prisma CLI path in JSON version output

0300afe

coderabbitai Bot approved these changes Jun 8, 2026

View reviewed changes

tensordreams changed the base branch from main to v7 July 21, 2026 12:06

tensordreams changed the base branch from v7 to main July 21, 2026 15:11

Merge branch 'main' into add-prisma-cli-path-version-7771

edb8da8

aqrln approved these changes Jul 21, 2026

View reviewed changes

dosubot Bot added the lgtm This PR has been approved by a maintainer label Jul 21, 2026

aqrln merged commit eba51ca into prisma:main Jul 21, 2026
243 checks passed

nagyminyo-cmyk mentioned this pull request Jul 23, 2026

feat(cli): output binary path in prisma -v output #29608

Closed

Navigation Menu

Uh oh!

feat(cli): show Prisma CLI path in version output - #29573

feat(cli): show Prisma CLI path in version output#29573
aqrln merged 3 commits into
prisma:mainfrom
SadmanPinon:add-prisma-cli-path-version-7771

SadmanPinon commented May 21, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented May 21, 2026 •

edited

Loading

❌ Failed checks (1 warning)

Uh oh!

CLAassistant commented May 21, 2026 •

edited

Loading

Uh oh!

tensordreams commented Jun 4, 2026

Uh oh!

SadmanPinon commented Jun 8, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

SadmanPinon commented May 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Demo / Review Proof

Validation

Uh oh!

coderabbitai Bot commented May 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Release Notes

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

CLAassistant commented May 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tensordreams commented Jun 4, 2026

Uh oh!

SadmanPinon commented Jun 8, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

SadmanPinon commented May 21, 2026 •

edited

Loading

coderabbitai Bot commented May 21, 2026 •

edited

Loading

CLAassistant commented May 21, 2026 •

edited

Loading