Lighthouse status fixes, scoped tokens, npm CLI, font loading, log deduplication, and visual diff consistency improvements.
- Fixed a bug where Lighthouse commit statuses would get stuck at “running” when a report failed to render. Now when a Lighthouse report errors out (like from a timeout or connection issue), the status on your pull request properly updates to “failed” instead of spinning forever.
- Access tokens can now be created with a role. Full access behaves as tokens do today. Sandbox agent is a new role for Sandbox previews, which are coming soon. A Sandbox agent token will be limited to the Sandbox previews it owns, so it cannot use the rest of the account.
- You can now install the Tugboat CLI from npm with
npm i -g @tugboatqa/cli (or run it via npx @tugboatqa/cli) — handy on Windows and anywhere Node is already around. Homebrew and dashboard binary downloads still work as before. - Preview splash pages (building, starting, suspended) now load their fonts reliably again. We fixed a caching quirk on the assets host that could block Poppins and icon fonts with a CORS error.
- Approving several failed Lighthouse reports in a row no longer flaps them back to Failed or leaves the PR check stuck while those approvals finish processing.
- Build logs in the dashboard no longer show the same lines twice while a build is streaming, even when teammates are watching the same build. Every line now appears once, so you only have to read about that failed
composer install one time. - Visual diffs now take the base preview screenshot with the same
fullPage, timeout, and waitUntil settings as the pull request screenshot, so slow-loading pages no longer show differences just because the base screenshot was taken too early. The visualdiff options still override these settings for the base preview screenshot.