Repository navigation
Follow the products' released versions: @prisma/composer-cli 0.28.0 -> 0.29.0; @prisma/composer 0.28.0 -> 0.29.0 - #341
prisma-bot wants to merge 1 commit into
Conversation
…> 0.29.0; @prisma/composer 0.28.0 -> 0.29.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>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. Summary by CodeRabbit
WalkthroughThe CLI manifest updates Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The CLI and Prisma packages will use Composer 0.29.0, with matching lockfile entries. No concrete merge-blocking risk is evident in these changes. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 2 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🧪 Generate unit tests (beta)
✨ Simplify code
🛠️ Fix failing CI checks 💡
Comment |
commit: |
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.28.0 -> 0.29.0; @prisma/composer 0.28.0 -> 0.29.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.