Repository navigation
chore(release): v0.32.0 - #370
Conversation
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>
|
✅ Gizmo reviewed f586f7f — posted 0 inline comment(s) this pass. Open findings: none Change walkthroughThis PR is the v0.32.0 release bump (0.31.0 → 0.32.0) for the prisma/composer monorepo. Merging it triggers the Publish to npm workflow; the release ships the single fix from #368 (the What changed. Every changed line in the diff is a version bump — a mechanical sweep across three kinds of edit:
pnpm-lock.yaml (the one file skipped from the checklist as generated) was regenerated with the bump, so the lockfile matches the manifests. Because every |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Comment |
commit: |
Release v0.32.0 (0.31.0 → 0.32.0). Merging this triggers the Publish to npm workflow.
It ships one change, #368, which fixes rough edges found while testing 0.31.0's local-dev commands through the real
prismabinary:prisma dev stoplists only what it actually stopped, and says so when nothing was running. It still sends a stop to every service and database, so one that is still starting is stopped too.prisma dev urlfor a stopped service says it is stopped and lists what stops an app, instead of blamingprisma devending.--nameand--freshhelp onprisma dev, and the--nameand--stagehelp onprisma deploy, say what each flag does in plain terms.The
prismaCLI picks this up in a follow-up that moves its Composer pin to 0.32.0.Agent: attila-51
🤖 Generated with Claude Code