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. AI Media still declares "node": ">= 22.0" and "yarn": ">= 1.6", and its GitLab CI runs Node 22.

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": ">= 22.0" and "yarn": ">= 1.6", and there is no packageManager.
  2. Open .gitlab-ci.yml: the step definitions ESLint job runs node:22, and the functional testing jobs download the Node tarball from latest-v22.x and then run yarn install through corepack, which gives Yarn Classic. .gitignore ignores .yarnrc.yml.

Proposed resolution

  • package.json engines: "node": ">= 24.0". Yarn moves to yarn@4.18.1 with the floor ">= 4.18.1", and .yarnrc.yml follows the Varbase standard (approvedGitRepositories, enableScripts, nodeLinker: node-modules, npmMinimalAgeGate: 0), which Yarn before 4.14.0 rejects. .gitignore no longer ignores .yarnrc.yml.
  • .gitlab-ci.yml: node:24 for the step definitions ESLint job, and the functional testing jobs download the Node tarball from latest-v24.x and check for v24. YARN_ENABLE_IMMUTABLE_INSTALLS is "false", since no lockfile is committed.
  • .gitlab-ci.yml: the composer and stylelint jobs set YARN_RC_FILENAME: .yarnrc.core.yml and YARN_NODE_LINKER: node-modules, so Drupal core's own Yarn 4.9.1 in those jobs does not read the project .yarnrc.yml, whose keys need Yarn 4.14.
  • The test scripts run node ./node_modules/@cucumber/cucumber/bin/cucumber.js: Yarn 4 does not expose the cucumber-js bin of a dependency of @vardot/varbase-e2e to yarn run, so yarn test failed with Yarn 4.18.1.
  • No lockfile is committed. .gitignore now ignores yarn.lock, package-lock.json and pnpm-lock.yaml, and .yarn/ too, so installs resolve from package.json.
  • Dependency ranges in package.json use carets, the way Drupal core writes them: exact versions, ~ and .x ranges become ^MAJOR.MINOR.PATCH, with no major bump.

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

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. Yarn 4.18.1 is the package manager.

Issue fork ai_media-3635731

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

rajab natshah created an issue. See original summary.

rajab natshah’s picture

Issue summary: View changes
Status: Active » Needs review

rajab natshah’s picture

Issue summary: View changes
Status: Needs review » Fixed
Issue tags: +ai_media-1.0.0-rc2

✅ Released ai_media-1.0.0-rc2

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.