Skip to content

v1.7.0

Latest

Choose a tag to compare

@kristof-siket kristof-siket released this 31 Aug 11:49
cd0add6

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.