Update Node.js to >= 24.0 for Varbase AI Content Review Base

Problem/Motivation

Node.js 20 reached end of life on 30 April 2026, and Drupal core main now requires "node": ">= 24.0" in core/package.json. Varbase AI Content Review Base still declares "node": ">= 20.0" and installs Node 22 in its GitLab CI.

Node 24 is the LTS line, latest v24.22.2, and it is one of the lines the November 2026 security releases will patch. Pinning the major picks those patches up with no further change. Local systems should use Node.js 24 or 26.

Steps to reproduce

1. On 1.0.x, open package.json: the engines say "node": ">= 20.0".
2. Open .gitlab-ci.yml: the functional test job downloads the Node tarball from latest-v22.x.

Proposed resolution

• package.json engines: "node": ">= 24.0".
• .gitlab-ci.yml: the functional test job downloads the Node tarball from latest-v24.x, and DRUPAL_CORE moves from 11.4.0 to 11.4.11, since Twig 3.30 breaks rendered pages on Drupal core 11.4.0 to 11.4.7.
• No lockfile is committed. .gitignore now ignores yarn.lock, package-lock.json and pnpm-lock.yaml. No Yarn change: the test suite installs with npm, and its range is already a caret.

AI-Generated: Yes

Remaining tasks

• ✅ File an issue
• ✅ Addition/Change/Update/Fix
• ✅ Testing to ensure no regression
• ➖ Automated unit testing coverage
• ➖ Automated functional testing coverage
• ➖ UX/UI designer responsibilities
• ➖ Readability
• ➖ Accessibility
• ➖ Performance
• ➖ Security
• ➖ Developer Documentation
• ➖ User Guide Documentation
• ❌ Reviewed by human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ✅ Release notes snippet
• ✅ Release varbase_ai_content_review_base-1.0.0-rc1

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• Node.js 24 or newer is now required, in the engines and CI.