Skip to content

ci: update Node.js test matrix from 18/20 to 20/22 - #656

Merged
PaulBoye-py merged 1 commit into
mainfrom
ci/update-node-test-matrix
Sep 9, 2026
Merged

PaulBoye-py merged 1 commit into
mainfrom
ci/update-node-test-matrix

Conversation

@PaulBoye-py

Copy link
Copy Markdown
Collaborator

Node 18 reached EOL in April 2025. Node 22 is the current LTS and is already used by the release job. Aligns the test matrix with the release environment.

Description

Updates the CI test matrix from ['18', '20'] to ['20', '22'].

Node.js 18 reached End of Life in April 2025 and no longer receives security patches. The release job already runs on Node.js 22.14.0, so the test matrix was inconsistent with the release environment.

No library code changed. CI configuration only.

Issue Ticket Number

N/A — routine CI maintenance, no issue ticket required.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Fix or improve the documentation
  • This change requires a documentation update

Checklist

  • I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
  • I have checked to ensure there aren't other open Pull Requests for the same update/change
  • I have performed a self-review of my own code
  • I have run tests locally to ensure they all pass
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes needed to the documentation

Node 18 reached EOL in April 2025. Node 22 is the current LTS
and already used by the release job. Aligns the test matrix with
the release environment.
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
next-cloudinary Ready Ready Preview Sep 9, 2026 4:05pm UTC

Request Review

@PaulBoye-py
PaulBoye-py merged commit 1a7d853 into main Sep 9, 2026
7 checks passed
@PaulBoye-py
PaulBoye-py deleted the ci/update-node-test-matrix branch September 9, 2026 16:08
eportis-cloudinary added a commit that referenced this pull request Sep 25, 2026
Brings 146 commits from main onto the v7 branch, including Next.js 16
compatibility (#657), the Node 20/22 CI matrix (#656), the Trusted
Publishers release plumbing, and three recent fixes: duplicate iframes on
CldUploadWidget unmount (#658), open() called before the widget script
loads (#659), and the docs Table component (#661).

Conflicts resolved as follows:

- CldVideoPlayer.tsx: union. Kept beta's 'use client' and named-only
  react import, added main's useState, which the merged body needs for
  isScriptLoaded/playerInitialized.
- next-cloudinary/package.json: kept beta's preconstruct build config,
  exports map, files and 7.0.0-beta.11 version; adopted the repository
  field main added in 554e2a0.
- package.json: kept @preconstruct/cli (beta's build needs it); dropped
  @colbyfayock/semantic-release-pnpm, which the merged .releaserc no
  longer references; took main's semantic-release 25 and
  @semantic-release/npm 13.
- pnpm-workspace.yaml: beta's list, which adds the test app - required
  because beta's test:app builds it via pnpm rather than npm install.
- tests/nextjs-app/package.json: main's Next 16 / React 19 versions plus
  beta's next-cloudinary workspace link.
- CHANGELOG.md: kept both release histories.
- pnpm-lock.yaml: regenerated against the merged manifests.

Also fixes CldUploadWidget.tsx, which git auto-merged without conflicting
but produced broken output: beta had dropped the default React import
while main's useUploadWidgetId helper calls React.useId and React.useRef.
The combination built fine and failed at prerender with "ReferenceError:
React is not defined". Restored the default import. Caught by test:app,
not by the unit tests.

Note: .releaserc auto-merged to main's @semantic-release/npm, which drops
beta's publishBranch "main|beta" setting. Branch gating now comes from
the top-level branches config alone.

This branch was successfully deployed

1 active deployment
Preview — 8299b700 Deployed Sep 9, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant