Skip to content

Update Cypress tests to use Node.js 22 #536

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jrhoads merged 1 commit into from
Dec 10, 2025
Merged

Update Cypress tests to use Node.js 22 #536

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/cypress_tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ jobs:
steps:
- uses: actions/setup-node@v4
with:
node-version: 18
node-version: 22
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for Node.js version specifications
echo "=== Checking for .nvmrc ==="
if [ -f .nvmrc ]; then
  cat .nvmrc
else
  echo "No .nvmrc file found"
fi

echo -e "\n=== Checking package.json engines field ==="
if [ -f package.json ]; then
  jq '.engines' package.json 2>/dev/null || echo "Cannot parse engines field or field not present"
else
  echo "No package.json found"
fi

echo -e "\n=== Checking for Node.js version references in docs ==="
find . -type f \( -name "*.md" -o -name "*.txt" \) -exec grep -l "node.*18\|nodejs.*18\|node-version.*18" {} \; 2>/dev/null | head -20

echo -e "\n=== Checking current Node.js version in workflow ==="
grep -n "node-version" .github/workflows/cypress_tests.yml 2>/dev/null || echo "Node version not found in workflow"

echo -e "\n=== Checking Cypress version in package.json ==="
if [ -f package.json ]; then
  jq '.devDependencies.cypress, .dependencies.cypress' package.json 2>/dev/null
else
  echo "No package.json"
fi

Repository: datacite/akita

Length of output: 362

🌐 Web query:

Cypress 13.6.3 Node.js 22 compatibility support

💡 Result:

Short answer: Cypress officially supports Node.js 22.x (per current system requirements), but v13.6.3 (released Jan 16, 2024) predates some Node‑22 related fixes — you may hit edge cases; upgrading to a newer Cypress patch/minor that explicitly addressed Node‑22 issues is recommended. [1][2]

Sources:

  • Cypress system requirements (lists Node.js 20.x, 22.x, >=24.x). [1]
  • Cypress changelog: 13.6.3 release notes (released Jan 16, 2024) and later changelogs with Node‑22 related fixes. [2]

Update Cypress to latest v13 patch for better Node.js 22 support.

The Node.js version is already updated to 22, but Cypress 13.6.3 (released January 2024) predates several Node.js 22 compatibility fixes. While the current version will work, upgrading Cypress to the latest v13 patch releases will provide better stability with Node.js 22.

Update the cypress dependency in package.json to the latest available v13 version to ensure all Node.js 22 related fixes are included.

🤖 Prompt for AI Agents 
.github/workflows/cypress_tests.yml lines 26-26: the CI is using node-version 22
so update the project to a Cypress v13 patch that includes Node.js 22 fixes;
open package.json and change the "cypress" dependency to the latest v13.x patch
(e.g. 13.<latest>) ensuring the semver constraint pins to that patch, then
update lockfile (npm install or yarn install) and commit the updated
package.json and package-lock.json/yarn.lock; if CI pins Cypress elsewhere
(scripts or Dockerfiles), update those references too and run the test suite
locally to confirm compatibility.

- name: Checkout
uses: actions/checkout@v4
- name: Cypress run
Expand Down