ci: also run unit tests on Node 26 - #175
Merged
Merged
Conversation
The matrix covered 22 and 24. Node 26 becomes LTS on 2026-10-28, under three months away, so testing it now makes the promotion a non-event rather than the moment incompatibilities surface. There is precedent for the matrix earning its keep: the rate-limit window-boundary flake fixed in PR #170 was first hit by the Node 24 job, not the Node 22 one. Breadth found it early even though the defect turned out not to be version-specific. Nothing blocks this. better-sqlite3 12.11.1 publishes a prebuild for Node 26's ABI (node-v147), so the native module installs without compiling, and the full suite already passes on 26 locally: 1,941 unit tests and 30 fuzz tests, lint clean. engines stays >=22. Testing on 26 proves the code runs there; it does not require it, and raising the floor would narrow who can install EgressView. The coverage gate and the fuzz campaign stay on 22 alone -- measuring coverage three times would only cost time.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why now
The matrix covered 22 and 24. Node 26 becomes LTS on 2026-10-28 — under three months away. Testing it now makes the promotion a non-event rather than the moment incompatibilities surface.
There is precedent for the matrix earning its keep: the rate-limit window-boundary flake fixed in #170 was first hit by the Node 24 job, not the Node 22 one. Breadth found it early even though the defect turned out not to be version-specific.
Nothing blocks it
better-sqlite312.11.1 publishes a prebuild for Node 26's ABI (node-v147), so the native module installs without compiling — verified against the published release assets.The full suite already passes on 26 locally: 1,941 unit tests, 30 fuzz tests, lint clean.
Scope
enginesstays>=22. Testing on 26 proves the code runs there; it does not require it, and raising the floor would narrow who can install EgressView.🤖 Generated with Claude Code