chore(release): v0.19.0

[wmadden-electric]

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

The only change since v0.18.0 is the ORM family moving from 8.0.0-rc.8 to 8.0.0-rc.10 (#291).

🤖 Generated with Claude Code

[prisma-gizmo]

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

Open findings: none

Change walkthrough

This is the release PR for v0.19.0: it bumps every workspace package from 0.18.0 to 0.19.0 and updates all inter-package workspace: version specifiers to match. Merging it triggers the Publish to npm workflow for the public packages.

• All 42 touched files are mechanical 0.18.0 → 0.19.0 bumps. Repo-wide verification at the head commit confirms the bump is complete: every workspace package.json reports version 0.19.0 (the only exceptions are the static reference apps under docs/design/04-inspirations/, which are not part of the release and were correctly left alone), no workspace: specifier anywhere still references 0.18.0, and no other 0.18.0 reference survives outside pnpm-lock.yaml.
• Scope: the only functional delta since v0.18.0 is the ORM family move to 8.0.0-rc.10 from chore(deps): move the ORM family to 8.0.0-rc.10 #291, which landed on main before this release commit — the release commit itself contains only version changes, so the diff is exactly what a release should contain.
• Coverage by area: examples bump versions plus workspace: references in dependencies, peerDependencies, and devDependencies (including the nested @store/* and @storefront-auth/* module packages); internal framework and Prisma Cloud packages bump matching @internal/* specifiers; the public packages (@prisma/composer, composer-cli, composer-prisma-cloud) keep private @internal/* deps confined to devDependencies, consistent with the repo's publish guard against private workspace dependencies; and the root package.json version, the integration test package, and the SKILL.md library_version metadata all track 0.19.0.
• Lockfile: pnpm-lock.yaml (the one file skipped from the checklist) was regenerated in the same commit and contains no stale 0.18.0 resolvers, so pnpm install --frozen-lockfile in CI remains consistent with the new specifiers.
• External dependency pins (alchemy beta, effect RC, ORM RC versions, @prisma/cli-engine) were intentionally untouched by this commit.

[coderabbitai]

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: b4ad14b6-5de3-4be9-964a-295088a0287c

---

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@292

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

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

commit: f0df80f

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

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