Describe the bug
as part of release 2.77.0 lambdas were updated from nodejs14 to nodejs 16.
https://github.com/aws/aws-cdk/releases/tag/v2.77.0
however it seems that some were missed - https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/custom-resources/lib/provider-framework/provider.ts
nodejs_14 is still being used
Expected Behavior
nodejs_16 to be used for all CDK generated lambdas since release 2.77.0
Current Behavior
NODEJS_14 is still used in some cases
Reproduction Steps
deploy CDK which uses custom provider.
Possible Solution
update all lambdas so they do not use NODEJS_14
Additional Information/Context
No response
CDK CLI Version
2.77.0
Framework Version
No response
Node.js Version
16.20.0
OS
Ubuntu standard:6.0
Language
Typescript
Language Version
Typescript 4.9.4
Other information
No response
Describe the bug
as part of release 2.77.0 lambdas were updated from nodejs14 to nodejs 16.
https://github.com/aws/aws-cdk/releases/tag/v2.77.0
however it seems that some were missed - https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/custom-resources/lib/provider-framework/provider.ts
nodejs_14 is still being used
Expected Behavior
nodejs_16 to be used for all CDK generated lambdas since release 2.77.0
Current Behavior
NODEJS_14 is still used in some cases
Reproduction Steps
deploy CDK which uses custom provider.
Possible Solution
update all lambdas so they do not use NODEJS_14
Additional Information/Context
No response
CDK CLI Version
2.77.0
Framework Version
No response
Node.js Version
16.20.0
OS
Ubuntu standard:6.0
Language
Typescript
Language Version
Typescript 4.9.4
Other information
No response