Upgrade cypress version

[AdityaJ2305]

Proposed Changes

• Fixes Upgrade Cypress CI's node version #9374

@ohcnetwork/care-fe-code-reviewers

Summary by CodeRabbit

• New Features

  • Enhanced test execution for forked pull requests with conditional environment variables for improved parallel processing.

• Chores

  • Updated Node.js version in the workflow configuration for Cypress tests.

[coderabbitai]

Walkthrough

The changes in this pull request update the GitHub Actions workflow for Cypress tests. The primary modification involves upgrading the Node.js version from "20" to "22.11.0". Additionally, new environment variables SPLIT and SPLIT_INDEX are introduced for forked pull requests to enable test splitting, while the CYPRESS_SPLIT_TESTS variable is set to "true" for these cases. The overall structure of the workflow remains intact, with existing steps for repository checkout, Docker container management, and artifact uploads preserved.

Changes

File	Change Summary
.github/workflows/cypress.yaml	Updated Node.js version to "22.11.0"; added SPLIT and SPLIT_INDEX for forked PRs; set CYPRESS_SPLIT_TESTS to "true".

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade Cypress CI's node version (#9374)	✅

Possibly related PRs

• fixed the condition in cypress video artefact upload #9149: This PR modifies the .github/workflows/cypress.yaml file, specifically addressing the conditions for uploading Cypress video artifacts, which relates to the workflow configuration changes made in the main PR.

Suggested reviewers

• rithviknishad

Poem

In the land of code where rabbits hop,
We’ve upgraded Node, let the tests not stop!
With splits and tricks, our workflow’s now bright,
Parallel tests, oh what a delight!
Hopping through CI, we’ll conquer the night! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for care-ohc ready!

Name	Link
🔨 Latest commit	6b103f9
🔍 Latest deploy log	https://app.netlify.com/sites/care-ohc/deploys/675970716b94640007b4643b
😎 Deploy Preview	https://deploy-preview-9375--care-ohc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.github/workflows/cypress.yaml (1)

Line range hint 108-134: Document test splitting strategy for forked PRs

The workflow introduces test splitting for forked PRs using CYPRESS_SPLIT_TESTS, SPLIT, and SPLIT_INDEX environment variables, but their purpose and behavior aren't documented.

Consider adding comments to explain:

        env:
+         # Enable test splitting for parallel execution
          CYPRESS_SPLIT_TESTS: "true"
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NODE_OPTIONS: --max_old_space_size=4096
          COMMIT_INFO_MESSAGE: ${{github.event.pull_request.title}}
          COMMIT_INFO_SHA: ${{github.event.pull_request.head.sha}}
+         # Variables for distributing tests across matrix jobs
          SPLIT: ${{ strategy.job-total }}
          SPLIT_INDEX: ${{ strategy.job-index }}

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between bd19bcb and 6b103f9.

📒 Files selected for processing (1)

• .github/workflows/cypress.yaml (1 hunks)

🔇 Additional comments (1)

.github/workflows/cypress.yaml (1)

71-71: 🛠️ Refactor suggestion

Consider using LTS Node.js version instead of Current

The upgrade to Node.js 22.11.0 raises some concerns:

1. Node.js 22 is currently in "Current" status, not LTS, which could lead to stability issues in CI
2. Using an exact patch version (22.11.0) might be too restrictive for maintenance

Let's verify the project's Node.js compatibility:

Consider one of these alternatives:

-          node-version: "22.11.0"
+          node-version: "20"  # Current LTS version

or if Node.js 22 is required:

-          node-version: "22.11.0"
+          node-version: "22.x"  # More flexible, allows patch updates

[github-actions]

@AdityaJ2305 Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌