fix: use electron browser in cypress [main]

[ronlavi2412]

Summary

• Change cypress run --browser chrome → cypress run --browser electron in package.json (developer consistency fix)

Why CI is not broken on this branch

On main, test-prow-e2e.sh calls npm run test-cypress-headless — not yarn run cypress. The test-cypress-headless script already defaults to electron:

node ... cypress run --env openshift=true --browser ${BRIDGE_E2E_BROWSER_NAME:=electron}

So the CI pipeline on this branch is not affected by the Chrome absence in tectonic-console-builder-v29.

Why this PR is still useful

The cypress script (used for local development: yarn/npm run cypress) still hardcodes --browser chrome, which will fail on any machine without Chrome. This PR makes the local developer experience consistent with what CI actually runs.

Companion PRs

CI builder standardization (openshift/release): openshift/release#82053

This series (all branches):

Branch	PR	Role
release-4.19	#263	Urgent — fixes active CI failure
release-4.21	#264	Consistency — CI already uses electron
release-4.22	#265	Consistency — CI already uses electron
main	#266	Consistency — CI already uses electron
release-4.20	#267	Prerequisite — must merge before openshift/release#82053
release-4.18	#268	Prerequisite — must merge before openshift/release#82053
release-4.17	#269	Prerequisite — must merge before openshift/release#82053

Test plan

• npm run cypress launches Cypress under Electron locally

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@ronlavi2412, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5bebbfe4-f2dd-436e-a92f-ebca60ccf5de

📥 Commits

Reviewing files that changed from the base of the PR and between 9b50dd7 and 0d45cf3.

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ronlavi2412

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ronlavi2412]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@ronlavi2412: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[Parthivk100]

/lgtm