Repository navigation
presets(aws-amplify): support node.js 22 and 24 runtimes - #4244
Conversation
AWS Amplify Hosting no longer supports Node.js 16 or 18 and now supports Node.js 20, 22, and 24. Update the runtime union accordingly and refresh stale references in JSDoc and the docs page (including the amplify.yml templates that still pinned `nvm use 18`). Ref: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-supported-features.html
|
@armujahid is attempting to deploy a commit to the Nitro Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
AWS Amplify Hosting no longer supports Node.js 16 or 18 and now supports Node.js 20, 22, and 24. Drop the obsolete
nodejs16.x/nodejs18.xliterals and addnodejs22.x/nodejs24.xto the runtime union.Also refreshes the JSDoc example and the docs page, including the
amplify.ymltemplates that still pinnednvm use 18.Default runtime is unchanged (
nodejs20.x, the minimum still supported by Amplify). Markdown examples usenodejs24.x/nvm use 24(current Node.js Active LTS).Note: removing
nodejs16.xandnodejs18.xfrom the union is a TypeScript-type breaking change, but those values are rejected at deploy time by Amplify, so leaving them in would be misleading. Happy to switch to a deprecation approach if preferred.