Bump browser-actions/setup-chrome from 1 to 2

[dependabot[bot]]

Bumps browser-actions/setup-chrome from 1 to 2.

Release notes

Sourced from browser-actions/setup-chrome's releases.

setup-chrome: v2.0.0

2.0.0 (2025-07-06)

⚠ BREAKING CHANGES

• Use chrome for testing as default (#632)

Features

• Use chrome for testing as default (#632) (3bb0bd6)

v2.0.0

2.0.0 (2025-07-06)

⚠ BREAKING CHANGES

• Use chrome for testing as default (#632)

Features

• Use chrome for testing as default (#632) (3bb0bd6)

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.

</tr></table> 

... (truncated)

Changelog

Sourced from browser-actions/setup-chrome's changelog.

Commits

• b94431e Release v2.1.0 at 5f2f9dae94e061474cbfa44c9901c5faee86f8e9
• 4c4260d Release v2.0.0 at 3289928922e4e14c8d0131d7da41090f078025bb
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.