Skip to content

ci: test against Node 18, 20, and 22 (full engines range)#66

Open
dmchaledev wants to merge 1 commit into
mainfrom
claude/nice-mendel-j1kunb
Open

ci: test against Node 18, 20, and 22 (full engines range)#66
dmchaledev wants to merge 1 commit into
mainfrom
claude/nice-mendel-j1kunb

Conversation

@dmchaledev

Copy link
Copy Markdown
Contributor

Problem

package.json declares "engines": { "node": ">=18.0.0" }, but CI only ran against Node 20. That means:

  • Node 18 (still in LTS maintenance until April 2025, widely deployed) — never tested
  • Node 22 (current LTS) — never tested

A regression on either version would ship to npm users undetected.

Fix

Add a strategy.matrix to the CI job so it runs on Node 18, 20, and 22 in parallel. No production code changes — purely additive CI improvement.

strategy:
  matrix:
    node-version: ['18', '20', '22']

Test plan

  • All three matrix legs (Node 18, Node 20, Node 22) pass typecheck, test, and build
  • No changes to source files, tests, or config other than ci.yml

https://claude.ai/code/session_01LCsREUiKF2K3rvpJyih1h4


Generated by Claude Code

The package declares engines >= 18 but CI only validated Node 20.
Node 18 is still in maintenance LTS and Node 22 is the current LTS,
so regressions on those versions would have gone undetected.

https://claude.ai/code/session_01LCsREUiKF2K3rvpJyih1h4
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.

2 participants