Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@
"@discordjs/core": "^1.2.0",
"@influxdata/influxdb-client": "^1.35.0",
"@influxdata/influxdb-client-apis": "^1.35.0",
"@prisma/client": "^6.19.0",
"@prisma/client": "^7.4.2",
"@rollup/plugin-alias": "^6.0.0",
"@sapphire/async-queue": "^1.5.5",
"@sapphire/bitfield": "^1.2.4",
Expand Down Expand Up @@ -112,7 +112,7 @@
"eslint-plugin-prettier": "^5.5.4",
"lint-staged": "^16.2.7",
"prettier": "^3.7.2",

This comment was marked as outdated.

"prisma": "^6.19.0",
"prisma": "^7.4.2",
"prisma-json-types-generator": "^3.6.2",
"taze": "^19.9.2",
"tsdown": "^0.17.2",
Comment on lines 112 to 118
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The upgrade to Prisma v7 requires an output field in the prisma/schema.prisma generator block. Its absence will cause the prisma generate command to fail during the build.
Severity: CRITICAL

Suggested Fix

Update the generator block in the prisma/schema.prisma file to include the required output field. For example, add output = "../node_modules/.prisma/client" to explicitly specify the generation path and comply with Prisma v7's requirements.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L112-L118

Potential issue: The pull request upgrades Prisma to v7, which introduces a breaking
change making the `output` field required in the `generator` block of
`prisma/schema.prisma`. The current schema file lacks this field. As a result, the `pnpm
prisma:generate` command, which is executed during the CI pipeline, will fail. This
prevents the Prisma Client from being generated, causing subsequent build steps to fail
due to unresolved imports from `@prisma/client` and blocking any deployment.

Did we get this right? 👍 / 👎 to inform future reviews.

Expand Down
Loading
Loading