Vizzly CLI v0.27.0 Release Notes

What's Changed

JSON Output Support (--json flag)
- All commands now support machine-readable JSON output
- Optional field selection: --json field1,field2
- Consistent output format with {status, data} or {status, error} structure
- Makes CLI fully scriptable and LLM-friendly
New Discovery Commands
- vizzly orgs - List organizations with access levels and project counts
- vizzly projects - List projects with optional --org filtering
- vizzly builds - List and query builds with pagination support
- vizzly comparisons - Query and search comparisons by build, ID, or name
- vizzly baselines - List all local TDD baselines with metadata
New Review Commands
- vizzly approve <comparison-id> - Approve a comparison
- vizzly reject <comparison-id> -r "reason" - Reject with detailed reason
- vizzly comment <build-id> "message" - Add comments to builds
User Authentication Fallback
- Config loader now falls back to user JWT from vizzly login
- Enables interactive CLI usage without project tokens
- Works alongside existing project token auth for CI/CD workflows
Developer Experience Improvements
- Help examples added to all new commands
- Workflow guidance in help output
- npm run cli script for local development

Node.js and npm Requirements
- Updated to use Node 22 with npm 11.5.1+ for Trusted Publishers
- Requires engines.node >= 22.0.0
npm Release Process
- Switched to OIDC Trusted Publishers for improved security
- No longer uses registry-url configuration
- Now uses GitHub-hosted runners for more reliable releases

Full Changelog: ruby/v0.2.1...v0.27.0