Repository navigation
Run CI and publish on Node 24 - #11
Merged
Merged
Conversation
Merged
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
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.
Run CI and publish on Node 24
Every pull request now fails at
npm ci, so lint, build and tests never run. Both workflows ask forlts/*, which moved to Node 26 when it became the LTS on 28 October.n8n-workflow pulls in isolated-vm 6.2.0, which ships prebuilt binaries for Node 22 and 24 only, so on 26
npm cihas to compile it from source. The publish job installs the same way, so without this pin the next release tag would fail to publish too.Verify: this PR's CI run passes.
Risk: none; revert to go back to lts/*.