Happo News
Get an email when we publish a new article or ship something noteworthy. Prefer to read in your own feed reader? Subscribe via RSS.
Recent articles
What's new in happo v7, and how to upgrade
Version 7 of the happo package turns on the checks that used to be opt-in, removes options Happo no longer needs, and fails on config options it doesn't know. This post lists each change, what it gets you, and what to change in your config to upgrade.
Say why when you reject a diff
On the new compare page, rejecting a diff can now come with a short note saying what's wrong. Everyone looking at the comparison sees it, and so does an AI agent working through the Happo MCP server.
The Happo review experience just got a big upgrade
The redesigned compare page groups diffs with the same change into one, lets you accept or reject each diff on its own, and carries your decisions over to later commits. A new dashboard comes with it. Both are available today as an opt-in.
Keep render errors out of your Happo baseline
When an example fails to render, Happo now reports the error as text instead of taking a screenshot of it. With the new blockApproval option in the Happo config, you can keep a comparison from being approved while its report has render errors.
Block HTTP requests to cut flake and lock down Happo workers
A new option in the happo npm package lets you allow-list the hostnames your snapshots may talk to. Requests to anything else never leave the worker, which means faster runs, a tighter security boundary, and a lot less flake. One customer went from about 2,000 flaky examples to about 20.