Release 2.0.0: the Prisma Next rebuild is a breaking change by SerhiyGreench · Pull Request #4 · imqueue/pg-prisma

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

SerhiyGreench · 2026-08-28T08:42:55Z

What does this PR do?

Bumps the package to 2.0.0 for the Prisma Next rebuild merged in #3.

A major rather than a minor, because a ^1.1.0 consumer would otherwise pick
this up and break on all three of these:

the peer moves from @prisma/client >=7 to @prisma/orm-postgres >=8.0.0-rc.8;
the ./codegen subpath export is gone, along with the Prisma 7 generator it
pointed at;
the four query extensions are no longer $extends arguments — they are
SqlMiddleware passed to postgres({ middleware }).

Version commit only; no source changes.

Type of change

Checklist

I have read the Contributing guide.
Tests added or updated, and the full suite passes locally (npm test) — 86 tests.
Docs / doc-blocks updated where relevant — n/a, version commit only.
The PR is focused on a single logical change.

Contribution terms (required)

I have read and agree to the @imqueue Contribution Terms.
I grant the project owner the right to license my contribution
commercially, royalty-free, my contribution stays available under
GPL-3.0, I keep my copyright, and I understand I will receive no fee for
it. If I did not agree, I would not be submitting this contribution.

Merge this with a merge commit, not squash or rebase. The v2.0.0 tag is
already on the remote and points at 5001561; the repo's "Tags are immutable
once pushed" ruleset means it cannot be moved. A squash or rebase would rewrite
that commit and leave the tag pointing at nothing reachable from master.

2.0.0
5001561

SerhiyGreench changed the title ~~2.0.0~~Release 2.0.0: the Prisma Next rebuild is a breaking changeAug 28, 2026

SerhiyGreench merged commit f438fb9 into masterAug 28, 2026
15 of 16 checks passed