Skip to content

chore(release): v0.2.0 - #143

Merged
wmadden merged 1 commit into
mainfrom
chore/release-v0.2.0
Jul 21, 2026
Merged

chore(release): v0.2.0#143
wmadden merged 1 commit into
mainfrom
chore/release-v0.2.0

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

Release v0.2.0. Merging this triggers the Publish to npm workflow, which ships every package at 0.2.0 to npm under dist-tag latest (via OIDC trusted publishing) and cuts a GitHub Release with auto-generated notes.

Bump produced by scripts/bump-minor.ts: root version 0.1.0 → 0.2.0, stamped across all 32 workspace packages in lockstep. pnpm check:publish-deps passes (no workspace:/catalog: leaks, exact internal pins).

@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c7d286d6-5e90-4033-91cf-08eee5a955ff

📥 Commits

Reviewing files that changed from the base of the PR and between d98e960 and c89e154.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (32)
  • examples/bucket/package.json
  • examples/cron/package.json
  • examples/env-param/package.json
  • examples/pn-widgets/package.json
  • examples/storage/package.json
  • examples/store/modules/catalog/package.json
  • examples/store/modules/orders/package.json
  • examples/store/modules/promotions/package.json
  • examples/store/modules/storefront/package.json
  • examples/store/package.json
  • examples/storefront-auth/modules/auth/package.json
  • examples/storefront-auth/modules/storefront/package.json
  • examples/storefront-auth/package.json
  • examples/streams/package.json
  • package.json
  • packages/0-framework/0-foundation/foundation/package.json
  • packages/0-framework/0-foundation/tsdown-config/package.json
  • packages/0-framework/1-core/core/package.json
  • packages/0-framework/2-authoring/nextjs/package.json
  • packages/0-framework/2-authoring/node/package.json
  • packages/0-framework/2-authoring/service-rpc/package.json
  • packages/0-framework/3-tooling/assemble/package.json
  • packages/0-framework/3-tooling/cli/package.json
  • packages/1-prisma-cloud/0-lowering/lowering/package.json
  • packages/1-prisma-cloud/1-extensions/target/package.json
  • packages/1-prisma-cloud/2-shared-modules/cron/package.json
  • packages/1-prisma-cloud/2-shared-modules/storage/package.json
  • packages/1-prisma-cloud/2-shared-modules/streams/package.json
  • packages/9-public/composer-prisma-cloud/package.json
  • packages/9-public/composer/package.json
  • test/integration/package.json
  • website/package.json

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting


Summary by CodeRabbit

  • Release
    • Updated the project and associated packages, examples, website, and integration tooling to version 0.2.0.
    • Aligned package versions across the release so related components work together consistently.
    • Updated example applications to the 0.2.0 release baseline without changing their scripts or runtime behavior.

Walkthrough

Package manifests across the repository were bumped from version 0.1.0 to 0.2.0. Workspace dependencies for framework, Prisma Cloud, public, integration, website, and example packages were updated to reference workspace version 0.2.0. Several example modules added Prisma packages to peer dependencies, and one build script message was reformatted without changing its control flow.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-v0.2.0
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch chore/release-v0.2.0

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@pkg-pr-new

pkg-pr-new Bot commented Jul 21, 2026

Copy link
Copy Markdown

Open in StackBlitz

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

commit: c89e154

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@wmadden
wmadden force-pushed the chore/release-v0.2.0 branch from 0304d78 to c89e154 Compare July 21, 2026 13:48
@wmadden
wmadden enabled auto-merge (rebase) July 21, 2026 13:48
@wmadden
wmadden merged commit 6667b93 into main Jul 21, 2026
16 of 18 checks passed
@wmadden
wmadden deleted the chore/release-v0.2.0 branch July 21, 2026 13:50
wmadden pushed a commit that referenced this pull request Jul 24, 2026
The v0.2.0 release PR (#143) went red across CI because the bump
rewrote workspace:<version> pins in every manifest but left
pnpm-lock.yaml at the old version, and CI installs with
--frozen-lockfile. bump-minor now runs `pnpm install --lockfile-only`
after set-version, the `pnpm bump-minor` script both docs already
reference actually exists, and the skill/versioning docs call out the
lockfile requirement.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wmadden pushed a commit that referenced this pull request Jul 24, 2026
The v0.2.0 release PR (#143) went red across CI because the bump
rewrote workspace:<version> pins in every manifest but left
pnpm-lock.yaml at the old version, and CI installs with
--frozen-lockfile. bump-minor now runs `pnpm install --lockfile-only`
after set-version, the `pnpm bump-minor` script both docs already
reference actually exists, and the skill/versioning docs call out the
lockfile requirement.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wmadden pushed a commit that referenced this pull request Jul 24, 2026
The v0.2.0 release PR (#143) went red across CI because the bump
rewrote workspace:<version> pins in every manifest but left
pnpm-lock.yaml at the old version, and CI installs with
--frozen-lockfile. bump-minor now runs `pnpm install --lockfile-only`
after set-version, the `pnpm bump-minor` script both docs already
reference actually exists, and the skill/versioning docs call out the
lockfile requirement.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

2 participants