Skip to main content

v1.0.2

This release makes it much easier to understand why a backup or restore did not complete: failed jobs now report accurate causes, and you are notified by email when something goes wrong. It also brings activity log improvements and further security hardening.

Improvements​

  • Backup & restore failure reasons: When a job fails, you now see an accurate, understandable cause including issues originating from the git provider (GitHub, Bitbucket) or the storage provider instead of a generic "process failed" message.
  • Failure notification emails: If a backup or restore fails, an email explaining the actual reason is now sent to you.
  • Activity logs: Filtering now runs on the server across all records for accurate results, IP addresses are captured more reliably.

Fixes​

  • Fixed the broken sign-in button link in the welcome email sent after signup.

Security​

  • API error responses in production no longer expose internal technical details.