Skip to content

chore(release): v0.21.0 - #302

Draft
wmadden-electric wants to merge 1 commit into
mainfrom
chore/release-v0.21.0
Draft

wmadden-electric wants to merge 1 commit into
mainfrom
chore/release-v0.21.0

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

Release v0.21.0. Merging this triggers the Publish to npm workflow.

Ships the local Postgres emulator fix from #298: @prisma/composer-prisma-cloud now declares and resolves its own @prisma/dev (^0.25.2), so messages over 64 KiB no longer crash prisma dev.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@coderabbitai

coderabbitai Bot commented Sep 18, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 482aaa93-1e75-4a16-9609-9fc2c7785af9


Comment @coderabbitai help to get the list of available commands.

@prisma-gizmo

prisma-gizmo Bot commented Sep 18, 2026

Copy link
Copy Markdown

✅ Gizmo reviewed 60dfc94 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This is the v0.21.0 release PR: a mechanical monorepo-wide version bump from 0.20.0 to 0.21.0. Merging it triggers the Publish to npm workflow; the release ships the already-merged #298 fix that lets @prisma/composer-prisma-cloud resolve its own @prisma/dev ^0.25.2 so the local Postgres emulator no longer crashes on messages over 64 KiB.

Version bump mechanics. Every workspace package — the private framework packages, prisma-cloud lowering/shared-module packages, the public @prisma/composer and composer-cli packages, plus examples, the integration-test package, and the website — had its version field and all workspace: specifiers bumped in lockstep, with no 0.20.0 specifiers or versions remaining in any package.json. The regenerated pnpm-lock.yaml matches: importers now carry workspace:0.21.0 specifiers, and the composer-prisma-cloud importer resolves @prisma/dev to 0.25.2. External pins (@prisma/cli-engine 0.4.0, @prisma/orm-postgres 8.0.0-rc.11, alchemy, effect, etc.) are correctly untouched.

Release inputs. The root package.json version at line 51 is what the publish workflow's version-determination script reads, so it drives the npm release. The skill metadata library_version was bumped to match, which keeps the skill consistent with the published @prisma/composer version.

Deliberately unchanged 0.20.0 references. Several spots still mention 0.20.0 but refer to the buggy @prisma/dev 0.20.0 that alchemy's ^0.20.0 pin pulls in — e.g. the regression-test comment in postgres.test.ts, the postgres.ts docs, check-prisma-dev-pin.test.mjs, gotchas.md, and the skill body. These are historical bug documentation, not release versions, so leaving them alone is correct.

The change follows the repo's documented release procedure (scripts/bump-minor.tsset-version.ts → lockfile regeneration).

@wmadden-electric
wmadden-electric marked this pull request as draft September 18, 2026 12:25
@wmadden-electric

Copy link
Copy Markdown
Contributor Author

Holding this release until #299 merges; the branch will be updated onto main afterwards so v0.21.0 includes it.

@pkg-pr-new

pkg-pr-new Bot commented Sep 18, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@302
npm i https://pkg.pr.new/@prisma/composer-cli@302
npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@302

commit: 60dfc94

@prisma-gizmo prisma-gizmo Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

New findings: none · trace

@prisma-gizmo prisma-gizmo Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

All Gizmo review threads are resolved and the head commit has been reviewed. Approving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant