chore: keep prisma CLI and client in one dependabot group - #15
Merged
Merged
Conversation
`prisma` is a devDependency and `@prisma/client` is a dependency, so the dependency-type groups split them across two PRs. The two packages must move together -- a mismatched pair fails `prisma generate` in postinstall: Error: Cannot find module '.../@prisma+client@7.10.0_prisma@6.2.1_.../generator-build/index.js' That is what broke #6/#7, then #10/#11, then #10/#14; each pair was closed unmerged. Group the two packages by name and exclude them from the dependency-type groups so Prisma upgrades arrive as a single reviewable PR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 18, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
prisma(the CLI) is a devDependency and@prisma/clientis a dependency, so thedependency-typegroups split them across two separate PRs. The two packages must move together — a mismatched pair failsprisma generateduringpostinstall:and from the other side:
This has now happened three times: #6/#7, then #10/#11, then #10/#14. Every one of those six PRs was closed unmerged because neither half could pass CI on its own.
What changed
Group
prismaand@prisma/*by name, and exclude them from bothdependency-typegroups so they cannot be split again. Prisma upgrades will now arrive as a single reviewable PR.Test plan
Note: this only fixes the grouping. The actual Prisma 7 upgrade still needs its own PR — it requires bumping client + CLI together, adding
prisma.config.ts, and movingdatasource.urlout ofprisma/schema.prisma.🤖 Generated with Claude Code