v1.7.0

Deploy failures now keep the CLI's precise reason

• On a failed deploy or destroy, the action defers to the failure report the Prisma CLI already recorded on the build (for example DEPLOY.PREFLIGHT_FAILED with the missing variable named), instead of overwriting it with a generic "exited with status N" message. The generic message is still recorded when the CLI crashed before it could report. (#15)
• The action passes PRISMA_BUILD_ID to the commands it runs, so the CLI reports into the action's build instead of deriving the run identity itself and risking a duplicate build.
• The post step no longer changes a build that already reached a final state, and keeps a recorded error message on cancellation.

The v1 tag now points at this release.

v1.6.0

Restores compatibility with the current unified prisma CLI.

• Invoke the top-level deploy commands (prisma deploy): the prisma composer subcommand family was removed in prisma@8.0.0-rc.8, which broke all earlier action releases (CLI.UNKNOWN_COMMAND).
• Bump the bunx fallback prisma-version default from 8.0.0-rc.7 to 8.0.0-rc.9.
• Require Bun >= 1.3.10: Bun <= 1.3.9 omits Content-Length on the CLI's artifact upload, failing deploys with an opaque HTTP 411. The action now fails fast with an error naming the bug and where to look for a stale Bun pin.

Known limitation: mode: destroy does not work against prisma@8.0.0-rc.9 (no top-level destroy command); Console-connected repositories get preview teardown from the platform's branch automation instead. See the README.

v1.5.0

Adds a no-build mode: build-command: none skips the build phase in both deploy and destroy modes, for apps with no build step (for example a stock Bun app that runs its TypeScript source directly). The exact value none is required — an empty input still defaults to npm run build, and any other value runs verbatim. Exercised end to end on a stock Elysia repo before tagging (#9). v1 now points here.

v1.4.1

Runs the repo's local Composer bin as bun run --bun prisma-composer, so the Composer CLI and the converge child it spawns both run under Bun. v1.4.0 ran the CLI under Bun but left the child on Node, which could not resolve the generated ./service.js import (#8). v1 now points here.

v1.4.0

Composer runs under Bun

• The deploy step now runs prisma-composer under Bun — Composer's own tested runtime (its e2e and docs deploys use bun node_modules/.bin/prisma-composer). Local bin: bun <bin> deploy …; fallback when no local bin: bunx --bun -p @prisma/composer-cli@<composer-version> prisma-composer.
• The action fails early with a clear message if bun is not on the runner. Add oven-sh/setup-bun@v2 (pinned) before this action; workflows generated by the Prisma platform after prisma/pdp-control-plane#4949 include it.
• Log label is now honest: composer=local bin (bun) / composer=<version> (bunx fallback).
• The user's app is still installed and built with its own toolchain; only the Composer deploy step changes runtime.

PR: #7

v1.3.0

Report the deployed preview URL (deployedUrl) on a successful deploy, so Prisma Console can link the live preview from the build. The action reads the *.prisma.build address from the deploy output and includes it in the success report (best-effort; a missing address never fails the deploy).

See #5.

v1.2.0

Deploy runs now report builds to the Prisma API: one build per workflow run (idempotent across re-deliveries via the run identity), phase and state updates as the run progresses, the failing step and error on failure, and cancellation from the post step when a run is interrupted. Reporting is best-effort by design: any reporting failure is a workflow warning and never affects the deploy. Requires no workflow changes; runs without a credential keep skipping cleanly.

v1.0.0

First tagged release. Install, build, and deploy a Composer-described repository from GitHub Actions: production on the default branch, a preview stage per branch, teardown on branch deletion, with a credential guard that skips cleanly when no token is present. The moving v1 tag tracks the newest backward-compatible release.