Follow the products' released versions: @prisma/composer-cli 0.20.0 -> 0.21.0; @prisma/composer 0.20.0 -> 0.21.0 - #278
Conversation
…> 0.21.0; @prisma/composer 0.20.0 -> 0.21.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 ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughThe pull request updates Composer dependencies from version 0.20.0 to 0.21.0. It changes the runtime and development dependencies in Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The update aligns the CLI and Prisma packages with Composer 0.21.0. No merge-blocking impact is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
commit: |
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.20.0 -> 0.21.0; @prisma/composer 0.20.0 -> 0.21.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.