chore: specify Google Chrome version in CI workflow

[pratapaprasanna]

Updated the CI workflow to install a specific version of Google Chrome (129.0.6668.100) instead of the latest version. This change ensures consistency in the testing environment by using a known version for all CI runs.

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Chores
  • Updated test environment configuration to pin Google Chrome to a specific version for improved test consistency and reliability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the GitHub Actions workflow to pin Google Chrome to a specific version (129.0.6668.100) by replacing the generic stable channel download with a hardcoded mirror URL and updating the corresponding deb file reference in the installation step.

Changes

Cohort / File(s)	Summary
CI workflow Chrome version pinning \.github/workflows/ci-test-custom-script\.yml	Updated the Chrome installation step to target version 129.0.6668.100 with hardcoded mirror URL instead of generic stable channel; renamed step accordingly

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify the hardcoded Chrome version URL remains accessible and is the intended version
• Confirm the specific version doesn't conflict with existing browser compatibility requirements

Possibly related PRs

• PR chore: update Google Chrome installation in CI workflow #41332: Also modifies the same Chrome installation workflow step but switches to a generic/current package instead of pinning a specific version—represents an alternative approach to the same CI dependency.

Suggested reviewers

• sharat87
• nidhi-nair

Poem

🌐 A Chrome version pinned, steady and true,
No drift through the tests, workflows renew,
From floating to fixed, stability blooms,
CI pipelines bright in their well-ordered rooms. ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/use/different/mirror/chrome/129

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69ae1df and 76ad530.

📒 Files selected for processing (1)

• .github/workflows/ci-test-custom-script.yml (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}