Chromatic v16.9.0 introduces a key enhancement allowing `chromatic skip` without a project token, simplifying CI/CD setups for visual regression testing.
Chromatic v16.9.0 Release Overview #
Date: 2026-05-06
Category: Test Automation
Key Changes #
Enhancement: Chromatic v16.9.0 introduces a notable update: the chromatic skip command no longer requires a project token. This change, detailed in #1310, provides greater flexibility for CI/CD environments where a token might not always be present or necessary for skipping a build. This update was contributed by Cody Kaup.
Official Release Notes: Chromatic v16.9.0
Impact for QA Teams #
QA engineers can now implement more flexible conditional skips in their CI/CD pipelines, reducing build failures related to missing tokens when a skip is intended. This streamlines automation scripts, particularly in complex monorepo setups or environments with varying access levels.
Frequently Asked Questions
What is the main change in Chromatic v16.9.0?
The primary update allows the `chromatic skip` command to function without requiring a project token, offering more flexibility in CI/CD setups.
Why is this change important for QA automation?
It simplifies conditional skipping of Chromatic builds in CI/CD pipelines, preventing failures when a token isn't present but a skip is desired, thus improving automation reliability.
Where can I find the official release notes?
The official release notes for Chromatic v16.9.0 are available on the Chromatic CLI GitHub repository: [Chromatic v16.9.0](https://github.com/chromaui/chromatic-cli/releases/tag/v16.9.0).
