Bump up for Prisma v7

[samchon]

This pull request updates the project to support Prisma v7 and modernizes the configuration and testing setup. The most important changes include upgrading Prisma-related dependencies, refactoring Prisma generator configurations, and improving the test structure to use directory-based test cases.

Dependency and Configuration Upgrades:

• Upgraded all Prisma-related dependencies (@prisma/client, prisma, and @prisma/generator-helper) in package.json to version 7, and updated peer dependencies to require Prisma v7 or higher.
• Changed Prisma generator provider from prisma-client-js to prisma-client and added explicit output directories in all relevant .prisma files (schema.prisma, test/drive/drive.prisma, test/implicit/implicit.prisma, test/summary/summary.prisma). [1] [2] [3] [4]

Test Structure and Automation Improvements:

• Added new prisma.config.ts files to each test directory (test/drive, test/implicit, test/summary) using defineConfig from Prisma v7, and removed direct url references from .prisma files in favor of config files. [1] [2] [3] [4]
• Refactored test/index.ts to iterate over test directories with their own config files, running prisma generate in each, instead of generating from individual .prisma files.

Workflow and File Management:

• Moved workflow permissions in .github/workflows/release.yml from the job level to the top-level permissions key for better GitHub Actions compatibility, and removed the use of NODE_AUTH_TOKEN for npm publishing. [1] [2]
• Renamed test schema files to reside within their respective directories for better organization. [1] [2] [3]

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​prisma/​generator-helper@​6.8.0 ⏵ 7.0.0	+1		+3
	@​prisma/​client@​6.8.0 ⏵ 7.0.0	+6		+1	+1
	prisma@​6.8.0 ⏵ 7.0.0			+1	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: package-lock.json → npm/prisma@7.0.0 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[Copilot]

Pull request overview

This PR upgrades the project from Prisma v6 to Prisma v7, adopting the new configuration pattern and modernizing the test structure. The upgrade includes breaking changes in how Prisma is configured, with datasource URLs now defined in separate prisma.config.ts files rather than directly in .prisma schema files.

Key Changes:

• Upgraded all Prisma dependencies (@prisma/client, prisma, @prisma/generator-helper) from v6 to v7 with updated peer dependencies
• Changed Prisma generator provider from prisma-client-js to prisma-client with explicit output directories
• Introduced prisma.config.ts files using Prisma v7's defineConfig API for datasource configuration

Reviewed changes

Copilot reviewed 12 out of 17 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
package.json	Updated Prisma dependencies and peer dependencies to v7.0.0
package-lock.json	Reflected dependency updates with new Prisma v7 packages
schema.prisma	Changed generator provider to "prisma-client", added output directory, removed datasource URL
prisma.config.ts	Added new config file with datasource URL configuration
test/drive/drive.prisma	Updated generator provider and path to executable, added output directory
test/drive/prisma.config.ts	Added new config file with datasource URL configuration
test/implicit/implicit.prisma	Updated generator provider and path to executable, added output directory
test/implicit/prisma.config.ts	Added new config file with datasource URL configuration
test/summary/summary.prisma	Updated generator provider and path to executable, added output directory
test/summary/prisma.config.ts	Added new config file with datasource URL configuration
test/index.ts	Refactored to iterate over directories with config files instead of individual .prisma files
test/drive/drive.md	Generated output file from updated schema (informational)
test/implicit/implicit.md	Generated output file from updated schema (informational)
test/summary/summary.md	Generated output file from updated schema (informational)
.gitignore	Added generated/ directory to ignore generated Prisma client output
.github/workflows/release.yml	Moved permissions to top level, removed NODE_AUTH_TOKEN (uses provenance instead)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The datasource URL is set to "localhost", which is likely a placeholder and not a valid database connection string. This could cause issues when running prisma generate. The URL should either be a valid connection string (e.g., "postgresql://localhost:5432/db") or use environment variables like env("DATABASE_URL").

Suggested change

	url: "localhost",
	url: env("DATABASE_URL"),

[Copilot]

The datasource URL is set to "localhost", which is likely a placeholder and not a valid database connection string. This could cause issues when running prisma generate. The URL should either be a valid connection string (e.g., "postgresql://localhost:5432/db") or use environment variables like env("DATABASE_URL").

Suggested change

	url: "localhost",
	url: 'env("DATABASE_URL")',

[Copilot]

The datasource URL is set to "localhost", which is likely a placeholder and not a valid database connection string. This could cause issues when running prisma generate. The URL should either be a valid connection string (e.g., "postgresql://localhost:5432/db") or use environment variables like env("DATABASE_URL").

Suggested change

	url: "localhost",
	url: env("DATABASE_URL"),

[Copilot]

The datasource URL is set to "localhost", which is likely a placeholder and not a valid database connection string. This could cause issues when running prisma generate. The URL should either be a valid connection string (e.g., "postgresql://localhost:5432/db") or use environment variables like env("DATABASE_URL").

Suggested change

	url: "localhost",
	url: 'env("DATABASE_URL")',