Take the dependencies forward, and two ranges that were holding them back - #8
Merged
Conversation
…back
`npm update` moves `@prisma/orm-postgres` to 8.0.0-rc.9, `@types/node`
to 26.5.1 and `oxlint` to 1.82.0. The lockfile was then regenerated from
nothing rather than edited, so nothing is carried over from a cached
resolution.
`@prisma/orm-postgres` moves to `>=8.0.0-rc.9` as a peer and
`^8.0.0-rc.9` in development. The two are raised together on purpose:
a peer floor of rc.9 beside a dev floor of rc.8 would let this
repository be built against a version it tells consumers is too old.
Two more could not move without changing their range, and both were
worth changing:
* `@types/pg` was pinned to exactly 8.20.4 while the `pg` it describes
is `^8.23.0`, so the types had fallen three minors behind the driver
they type. It is `^8.23.1` now, tracking the same line as `pg`
itself. The pin arrived with the Prisma Next rebuild and carried no
reason with it.
* `oxfmt` sat at `^0.65.0`, and a caret under `0.x` is patch-only, so
0.67.0 was out of reach. Taken deliberately rather than
automatically, because a formatter's minor version is where its
output changes: `format:check` passes on all 36 files unchanged, so
it reformats nothing here.
`@types/node` reports 22.20.2 as `latest` and is left alone — that tag
is older than the 26.x line this package is on, so taking "latest"
would be a downgrade of four majors.
Build, lint, format and all 90 tests pass on the regenerated tree.
SerhiyGreench
force-pushed
the
update-dependencies
branch
from
September 10, 2026 09:41
ee76e6f to
c6f3f02
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
npm updatemoves@prisma/orm-postgresto 8.0.0-rc.9,@types/nodeto 26.5.1 andoxlintto 1.82.0. The lockfile was regenerated from nothing —rm -rf node_modules package-lock.json && npm install— rather than edited, so nothing is carried over from a cached resolution, andnpm cireproduces it.@prisma/orm-postgresmoves to>=8.0.0-rc.9as a peer, and^8.0.0-rc.9in development. The two are raised together on purpose: a peer floor of rc.9 beside a dev floor of rc.8 would let this repository be built against a version it tells consumers is too old.Two more could not move without changing their range, and both were worth changing:
@types/pgwas pinned to exactly8.20.4while thepgit describes is^8.23.0, so the types had fallen three minors behind the driver they type. It is^8.23.1now, tracking the same line aspgitself. The pin arrived with the Prisma Next rebuild and carried no reason with it.oxfmtsat at^0.65.0, and a caret under0.xis patch-only, so 0.67.0 was out of reach. Taken deliberately rather than automatically, because a formatter's minor version is where its output changes —format:checkpasses on all 36 files unchanged, so it reformats nothing here.@types/nodeis left alone. npm reports22.20.2aslatest, which is older than the 26.x line this package is on — taking "latest" would be a downgrade of four majors.Verified on the regenerated tree:
npm ci,tsc --noEmit,format:check,lint, and 90/90 tests on Node 22 and 24.