chore(deps): bump next to 16.2.12, align @prisma/adapter-pg to 7.9.1 - #41
Merged
Conversation
Two version skews left behind by the dependency PRs merged in #36-#40: - #38 moved eslint-config-next to 16.2.12 while next stayed on 16.2.11. Both are pinned exactly and have always been bumped in lockstep (#29); 16.2.12 is the same release on both sides (docs backports + TypeScript 7 support). - #36/#40 moved the Prisma CLI and client to 7.9.1, but @prisma/adapter-pg sat inside its ^7.9.0 range, so npm never refreshed the lockfile entry. Prisma expects the CLI, client and driver adapter to share one version. Dependabot opened no PR for either: next 16.2.12 was published on 2026-07-25, by which point the five dependency PRs had filled open-pull-requests-limit (5), and adapter-pg needed only a lockfile refresh. The lockfile change is limited to next/@next/swc-* 16.2.11 -> 16.2.12, @prisma/{adapter-pg,debug,driver-adapter-utils} 7.9.0 -> 7.9.1, and the dedupe of two now-redundant nested @prisma/debug and @emnapi entries.
The lockfile in the previous commit was generated by npm 11 / node 24 on
the host, which pruned the optional @emnapi/{core,runtime} entries reached
through the wasm32-wasi fallbacks of @tailwindcss/oxide and @rolldown.
CI runs node 22 (per .nvmrc, npm 10.9.8), where `npm ci` refuses the
resulting package.json/lock mismatch.
Regenerated with npm 10.9.8 inside node:22-bookworm-slim, so the diff
against main is now confined to the intended changes: next + @next/swc-*
16.2.11 -> 16.2.12, @prisma/{adapter-pg,debug,driver-adapter-utils}
7.9.0 -> 7.9.1, plus the dedupe of two nested @prisma/debug entries.
Verified under node 22: npm ci, prisma generate, lint, tsc --noEmit,
vitest 23/23, next build.
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.
Follow-up to the five Dependabot PRs merged today (#36–#40). Both changes are version alignments that Dependabot did not — and would not — propose on its own.
What
nexteslint-config-nextto 16.2.12; the two are pinned exactly and have always moved in lockstep (#29)@prisma/adapter-pgContext
next.
eslint-config-next@16.2.12andnext@16.2.12are the same upstream release (docs backports + Fixes to support TypeScript 7). Leavingnexta patch behind its lint config is exactly the kind of skew #29 avoided by bumping both together.@prisma/adapter-pg. The manifest range
^7.9.0already admits 7.9.1, butnpm installdoes not refresh a satisfied lockfile entry, so the adapter stayed on 7.9.0 whileprismaand@prisma/clientwent to 7.9.1. Prisma treats the CLI, client and driver adapter as one versioned set —lib/prisma.tsconstructsnew PrismaClient({ adapter }), so these two packages share an internal interface.Why no Dependabot PR.
next16.2.12 was published 2026-07-25, by which time #36–#40 had filledopen-pull-requests-limit: 5, so the sixth PR was never created.@prisma/adapter-pgneeded only a lockfile refresh, which Dependabot does not raise for an in-range dependency.Changes
package.json/package-lock.jsononly. The lockfile diff is confined to:next+ all nine@next/swc-*binaries: 16.2.11 → 16.2.12@prisma/adapter-pg,@prisma/debug,@prisma/driver-adapter-utils: 7.9.0 → 7.9.1@prisma/debugentries and two@emnapi/*entriesNo new packages, no removals beyond those dedupes.
Verification
Local run on this branch, all green:
npx prisma generatenpm run lint— no issuesnpx tsc --noEmit— no errorsnpm run test— 23/23 passingnpm run build— 8 routes generatednpm auditis unchanged at 9 high, all dev-onlybrace-expansion/minimatchreached througheslintandtypescript-eslint; unrelated to this PR.