Follow the products' released versions: @prisma/composer-cli 0.18.0 -> 0.19.0; @prisma/orm-toolchain 8.0.0-rc.8 -> 8.0.0-rc.10; @prisma/composer 0.18.0 -> 0.19.0 - #263
Conversation
…> 0.19.0; @prisma/orm-toolchain 8.0.0-rc.8 -> 8.0.0-rc.10; @prisma/composer 0.18.0 -> 0.19.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>
|
Duplicate of #261, which carries the same three pin moves and already has a green CI run and conformance pass. The workflow itself now works up to the pull request: with prisma-bot added as a collaborator the push succeeds; the remaining failure is |
|
Caution Review failedThe pull request is closed. ℹ️ 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)
Knowledge base: Disabled due to Summary by CodeRabbit
WalkthroughUpdated ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Opened automatically by update-product-versions.yml, following the products' release dist-tags (@prisma/composer-cli 0.18.0 -> 0.19.0; @prisma/orm-toolchain 8.0.0-rc.8 -> 8.0.0-rc.10; @prisma/composer 0.18.0 -> 0.19.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.