Closed iliapolo closed 4 months ago
False alarm. The warnings are due to an old version of CDK:
epolon@bcd07455aba8 ~
❯ npx --yes aws-cdk@2.139 --version [16:52:40]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! This software has not been tested with node v22.5.1. !!
!! Should you encounter odd runtime issues, please try using one of the supported release before filing a bug report. !!
!! !!
!! This software is currently running on node v22.5.1. !!
!! As of the current release of this software, supported node releases are: !!
!! - ^20.0.0 (Planned end-of-life: 2026-04-30) !!
!! - ^18.0.0 (Planned end-of-life: 2025-04-30) !!
!! !!
!! This warning can be silenced by setting the JSII_SILENCE_WARNING_UNTESTED_NODE_VERSION environment variable. !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2.139.1 (build b88f959)
epolon@bcd07455aba8 ~
❯ npx --yes aws-cdk@2.140 --version [16:52:46]
2.140.0 (build 46168aa)
Node 22 support was added in @jsii/check-node@1.98.0
. The first version of CDK that picked up this version is 2.140.0
.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
Using the CDK cli with Node22 produces the following warning:
It happens as soon as the CDK cli is loaded, see: https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/cli.ts#L2
However, this is actually inaccurate, because support for Node22 was added a while back, and it exists in our testing matrix as well. For example:
Looks like there's either a bug in how we determine tested versions, or we missed something when adding node 22 support.