CI Resilience & Quality of Life
A batch of improvements to make Vizzly play nicer in CI environments. The vizzly finalize command now exits gracefully when no build exists (warns instead of failing your pipeline). You can set build names via the VIZZLY_BUILD_NAME environment variable instead of CLI flags. And if the Vizzly API returns a 5xx error, your CI won't fail – we'll warn and continue. For enterprises, users signing up with email/password now auto-join their org when their email domain matches a configured SSO domain.
What’s new
- ✓ Resilient finalize command: warns + exits 0 when no build exists (use --strict for old behavior)
- ✓ VIZZLY_BUILD_NAME environment variable for cleaner CI config
- ✓ Graceful 5xx error handling – CI continues with a warning instead of failing
- ✓ SSO domain auto-join for email/password signups (previously only worked with Google OAuth)
- ✓ Helpful debugging hints in verbose mode when builds are missing