Releases: browser-actions/setup-chrome
v2.1.0
setup-chrome: v2.1.0
v2.0.0
2.0.0 (2025-07-06)
⚠ BREAKING CHANGES
- Use chrome for testing as default (#632)
Features
Migration guide for v2.0.0
1. Installer Changes on Channel Name Installs
If you are using the channel name (stable, beta, dev, or canary) to install the browser, the new version of the action installs the browser from [Chrome for Testing][] instead of the official installer. Please check if your workflow is using the expected browser binary version with the new version of the action.
The installed browser binary with the channel name is as follows:
| Platform | New Binary Path |
|---|---|
| Linux | chrome |
| macOS | Google Chrome for Testing |
| Windows | chrome.exe |
On Windows runner, the installed location is changed from C:\Program Files to $RUNNER_TOOL_CACHE.
2. Cache Directory Changes
If you are self-hosted runner and installing the browser with the channel name to speed up the runner setup, please update your cache directory on your runners. The cache directory has been changed from chromium to chrome and ensure that your workflow is using the new cache directory.
3. Default Version Changes
If you don't specify chrome-version parameter in your workflow, please ensure that your workflow will install the expected version of Chrome for Testing. The default version is the stable channel version of Chrome for Testing instead of the latest version. To install the latest version, you need to specify chrome-version: latest in your workflow.
# v1
- name: Install the stable version of Chrome for Testing
uses: browser-actions/setup-chrome@v1
with:
chrome-version: stable
- name: Install the latest version of Chrome for Testing
uses: browser-actions/setup-chrome@v1
# v2
- name: Install the stable version of Chrome for Testing
uses: browser-actions/setup-chrome@v2
- name: Install the latest version of Chrome for Testing
uses: browser-actions/setup-chrome@v2
with:
chrome-version: latest