Conversation
|
| } | ||
| > | ||
| At least one of your projects uses Node 21: deployments will fail from 5 October. | ||
| At least one of your projects uses Node 21: new deployments from 5 October will switch to using Node 24. |
There was a problem hiding this comment.
🔍 Confirm the promised Node 24 rollout
The CLI image map still maps node to Node 21, and resolveDeploymentRuntime has no date-based switch. Confirm the promised transition ships by 5 October.
Was this helpful? React with 👍 or 👎 to provide feedback.
| } | ||
| > | ||
| At least one of your projects uses Node 21: deployments will fail from 5 October. | ||
| At least one of your projects uses Node 21: new deployments from 5 October will switch to using Node 24. |
There was a problem hiding this comment.
🔍 Consider a server change note
This customer-facing deployment guidance changes without the .server-changes/ note required for user-visible webapp changes. Confirm whether the correction merits a release note.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
|
Closing in favor of applying this change through the private repository. |
Summary
Updates the Node 21 runtime banner to explain that new deployments from 5 October will switch to Node 24, rather than fail.