v0.8.1

A patch release for contract applications with a database on Zerops: the schema check and the isolation tests no longer run inside the readiness window.

Upgrade steps for operators

• None on the installation. fabrika platform upgrade and each application's next deploy move the checks; the application needs no package update.
• A version deployed before the upgrade keeps its old start script until its next deploy, so a restart of it still runs the checks inside the readiness window. Redeploy an application whose checks take long.

Fixes

• Zerops: fabrika db codegen --verify and fabrika db test-isolation run as init commands, after the migrations, from a generated fabrika/verify.generated.sh. They used to run in the start script, inside the 180 s readiness window an application cannot raise: an application with many generated cases (605 took almost three minutes on a small database) failed with DEPLOY_FAILED although every check passed. A failed init command still stops the activation, so a stale schema module or a failed generated case keeps the previous version serving. The start script no longer runs the migrations a second time.
• A DEPLOY_FAILED version says why it may have failed: an init command failed or the readiness check never answered, naming the migrations, the schema check and the isolation tests for a contract application with a database.
• Verified on a live Zerops account: the readiness window opens only after the init commands, and an init command may run at least 240 s.

Full changelog: v0.8.0...v0.8.1