Twilio Changelog | Jan. 21, 2026
Segment Functions: Node.js v22 becomes the default runtime on January 31, 2026
Starting January 31, 2026, any new function customers create will default to Node.js v22. Existing functions will keep running on Node.js v18, and they'll only move to v22 when customers choose to redeploy them.
Authorization, execution behavior, and APIs all work exactly as they did before. If customers aren’t planning to modify or redeploy a function, there's nothing they need to do.
When customers are ready to move existing functions to the new runtime, they can follow the path that matches their workflow:
Via the Functions Editor UI: Navigate to Catalog > Functions, select the target function, and click Save & Deploy. This will rebuild and deploy the function on Node.js v22.
Via the API:
Source functions: Use the Create Function Deployment endpoint.
Other function types: Use the Update Function endpoint.
What to check before redeploying functions to Node.js v22
Most Node.js upgrades go smoothly, but it's worth double-checking a few things:
Review dependencies: Check function packages for Node.js v22 compatibility.
Test first: Test redeployments in a staging or development environment before pushing to production.
Monitor critical flows: Pay extra attention to business-critical functions or those using older packages.
Need a hand?
These resources will help: