Follow the products' released versions: @prisma/composer-cli 0.21.0 -> 0.22.0; @prisma/composer 0.21.0 -> 0.22.0 - #285
Conversation
…> 0.22.0; @prisma/composer 0.21.0 -> 0.22.0 Opened automatically (update-product-versions.yml); merging ships a dev version of the CLI. A real release stays a human act. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughUpdated Composer dependency declarations from version 0.21.0 to 0.22.0 in the CLI and Prisma package manifests. The CLI test now checks the composer section path relative to the directory containing Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The Composer upgrade and config-path expectation are consistent with the repository’s dependency and path-resolution behavior; no concrete merge-blocking regression is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
… against its config file composer 0.22.0 resolves the composer section's relative configPath against the prisma.config.ts that declared it, not against the process cwd (prisma/composer#262). The bin test still expected the cwd-based path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
commit: |
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.21.0 -> 0.22.0; @prisma/composer 0.21.0 -> 0.22.0). Merging publishes a
devversion of the CLI; the conformance checks on this pull request are what stand between a product release and that dev build.