Skip to content

v0.11.0-dev.4

v0.11.0-dev.4: Retire destroy and log from the composer command family (#253)
@wmadden-electric wmadden-electric tagged this 22 Aug 08:58 
* feat(cli)!: retire destroy and log from the composer command family

The 2026-08-21 PM review dropped destroy and log from the surface the
prisma bin mounts, and prisma-cli has been filtering them out of the family
(COMPOSER_DROPPED_COMMANDS). createComposerFamily() now ships deploy and
dev only, with no redirects, so hosts can mount it as-is.

The retirement applies to the family, not to prisma-composer itself:
createComposerCli mounts the destroy and log definitions on top of the
family, so the bin's surface is unchanged (deploy, destroy, dev, log).
dev's help drops its 'run `log <entry>`' pointer — that text also renders
under the prisma bin, where log doesn't exist.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

* fix(examples): give cron's destroy script the --production target it was missing

A bare destroy is an error — the script could never have succeeded; its
siblings all pass --production.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

---------

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Assets 2
Loading