Skip to content

chore: add Node.js 22.x, 23.x, 24.x, 25.x to CI matrix#51

Merged
UlisesGascon merged 4 commits intojshttp:masterfrom
imangas:chore/ci-add-missing-node-versions
Jan 7, 2026
Merged

chore: add Node.js 22.x, 23.x, 24.x, 25.x to CI matrix#51
UlisesGascon merged 4 commits intojshttp:masterfrom
imangas:chore/ci-add-missing-node-versions

Conversation

@imangas
Copy link
Contributor

@imangas imangas commented Dec 8, 2025

Add Node.js 22.x - 25.x to CI matrix

Description

This PR adds support for testing on newer Node.js versions in the CI workflow.

Changes

  • Added Node.js 22.x, 23.x, 24.x, and 25.x to the CI test matrix
  • No changes to existing version configurations
  • Fixed Node.js 0.6 build by adding Ubuntu Bionic GPG key (required after Ubuntu Bionic EOL)

Node.js versions

Version Status
Node.js 0.6 ✅ Fixed (added GPG key)
Node.js 0.8 - 21.x ✅ Unchanged
Node.js 22.x New
Node.js 23.x New
Node.js 24.x New
Node.js 25.x New

@imangas
Copy link
Contributor Author

imangas commented Jan 7, 2026

Update

CI coverage for Node.js v0.6 was removed (commented)

Changes

  • basic-auth-connect: Extend the GitHub Actions test matrix up to Node.js 25 (including 23/24/25) and ensure each matrix entry defines node-version.
  • jshttp-content-type: Comment out all Node.js 0.6-related CI code (the matrix.include entry and the special install/toolchain setup).

Why Node.js 0.6 was removed

Node.js 0.6 is an extremely old runtime and running it in CI requires a dedicated, outdated toolchain/OS package setup. We are disabling it for now so the pipeline remains reliable; re-enabling 0.6 will require revisiting and maintaining that installation path separately.

Notes

  • No runtime or API changes — CI-only.

@UlisesGascon UlisesGascon self-assigned this Jan 7, 2026
@UlisesGascon UlisesGascon merged commit 7028827 into jshttp:master Jan 7, 2026
31 checks passed
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