feat: Remove Node 18 support; add Node 24 support #476
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.
New Pull Request Checklist
Issue Description
Related issue: #279
Updates Node.js version support to align with active LTS versions by dropping Node 18 (EOL) and adding Node 24.
Approach
package.jsonengines.nodefrom18 || 20 || 22to20 || 22 || 24.github/workflows/ci.ymltest matrix to replace Node 18 with Node 24TODOs before merging
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
exp.host/usr/local/bin/node node ./node_modules/.bin/jasmine(dns block)fcm.googleapis.com/usr/local/bin/node node ./node_modules/.bin/jasmine(dns block)www.googleapis.com/usr/local/bin/node node ./node_modules/.bin/jasmine(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.