v1.6July 25, 2026
Failed builds now tell you why
- Every failure gets a cause. When a build fails, PreviewDrop runs 36 diagnostic rules over the build log and stores the result on the deployment — missing Django
ALLOWED_HOSTS, an unset NextAuth secret, an unrun Prisma migration, out-of-memory, port already in use, crash loops, and 30 more. The reason shows up in the deployments table, the activity feed, the Slack message, and the PR comment. Previously the product knew that a build broke and never why. - Build logs are kept. The log is snapshotted onto the deployment row at the moment of failure, so the evidence is still there when you come back to it tomorrow. Roughly 4 in 10 failed builds used to have no retrievable log at all.
- Fix-it deep links. When the cause is a missing or wrong environment variable, the failure links straight to that project's Variables tab.
- Failure-cause breakdown. The dashboard groups your failures by cause, so a project failing 50% of its builds shows you the one rule responsible instead of a wall of red.
- Referral program actually works. The referral flow had never credited a single account since launch — signups through a referral link were recorded but the bonus project slot was never granted. Fixed, and existing referrals were backfilled.
- Landing page rendering fixed. A Content-Security-Policy rule was blocking JavaScript and web fonts on the home and pricing pages for a large share of visitors. Both now render as designed.
- Preview lifetime corrected on pricing. The comparison table understated preview lifetimes by up to 10x. The real numbers are 4 hours on Free, 24 hours on Starter, 3 days on Pro, and 7 days on Team.