test(e2e): run prisma init from the local tarball in the corepack test

[tensordreams]

Summary

The prisma-init-corepack e2e test fails on every CI run (for example, this shard on #30180, and the same shard on the v7 tip's own CI run from 2026-08-27, before that PR existed).

Cause: the test runs pnpm dlx prisma init. dlx ignores the locally installed package and fetches prisma@latest from the registry — and latest is Prisma 8 (8.0.0-rc.12 today; Prisma 7 moved to the prev dist-tag). The v8 CLI rejects the fixture's Prisma 7 prisma.config.ts with CLI.CONFIG_MISSING_MARKER. The test was green on 2026-08-17 and red by 2026-08-27, matching the dist-tag transition, and can never be green again in this form.

Fix: run pnpm exec prisma init instead. The fixture already installs the prisma tarball under test as a devDependency, so exec makes the test hermetic and exercises the v7 CLI this branch builds. This matches the sibling prisma-init-bun test, which also runs the locally installed CLI.

The corepack regression coverage this test exists for (#28504) is unchanged: prisma init still executes in a corepack enabled container through a corepack-managed pnpm (packageManager: pnpm@10.15.1).

Testing performed

• Read the failing job log: the error envelope comes from the v8 CLI (CLI.CONFIG_MISSING_MARKER, "most likely a Prisma 7 config"), immediately after dlx downloads prisma from the registry.
• Verified registry state: prisma dist-tags are latest: 8.0.0-rc.12, prev: 7.10.0.
• The e2e shard on this PR's CI is the verification that the test passes again.

Related PRs

• ci: update github.repository checks for the rename to prisma/orm #30180 (v7 github.repository guards) — its failing e2e check is this same pre-existing test failure, plus a pnpm audit Lint failure that is advisory-driven and unrelated.

Summary by CodeRabbit

• Tests
  • Updated the Prisma initialization end-to-end test to run the locally installed Prisma package.
  • Improved test reliability by avoiding unexpected package retrieval during setup.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Team

Run ID: bfa53ab3-ef75-4e5f-91bf-c822aa6ed866

📥 Commits

Reviewing files that changed from the base of the PR and between 6ec4a6a and c0dba31.

📒 Files selected for processing (1)

• packages/client/tests/e2e/prisma-init-corepack/_steps.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The Prisma init Corepack E2E test now runs pnpm exec prisma init instead of pnpm dlx prisma init. This uses the installed Prisma package.

Changes

Prisma init E2E test

Layer / File(s)	Summary
Execute the installed Prisma package packages/client/tests/e2e/prisma-init-corepack/_steps.ts	The test invokes the installed Prisma package with pnpm exec prisma init instead of fetching it with pnpm dlx.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to c0dba

This localized test-only change makes the corepack test use the branch’s locally installed Prisma CLI, with no actionable merge-blocking risk remaining after normal checks and review.

Suggested reviewers: aqrln

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: the Corepack E2E test runs Prisma Init from the local tarball.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch v7-e2e-init-corepack-local-cli

---

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

[github-actions]

size-limit report 📦

Path	Size
packages/client/runtime/index-browser.js	2.29 KB (0%)
packages/client/runtime/index-browser.d.ts	3.37 KB (0%)
packages/cli/build/index.js	110 B (0%)
packages/client/prisma-client-0.0.0.tgz	25.59 MB (0%)
packages/cli/prisma-0.0.0.tgz	13.52 MB (0%)
packages/bundle-size/da-workers-libsql/output.tgz	1.28 MB (0%)
packages/bundle-size/da-workers-neon/output.tgz	1.35 MB (0%)
packages/bundle-size/da-workers-pg/output.tgz	1.34 MB (0%)
packages/bundle-size/da-workers-planetscale/output.tgz	1.28 MB (0%)
packages/bundle-size/da-workers-d1/output.tgz	1.26 MB (0%)