Describe the feature
On February 6, AWS announced the release of NodeJS puppeteer runtimes 6.2 & 5.2, and python selenium runtime 2.1, and announced that all non-deprecated older versions will be deprecated on March 8th. Today, we got an email from AWS saying that new lambda runtimes will be deployed on March 19th and that the changes will not be backwards compatible with current puppeteer versions so we have to upgrade our runtimes
Those versions do not exist in the latest CDK version, so we need them to be added so that we can update our runtimes, test and deploy to production before the cutoff time
Use Case
AWS will upgrade the lambda runtimes to a non-compatible version with the current puppeteer runtimes, which will break our synthetic canaries.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.128
Environment details (OS name and version, etc.)
MacOS 14
Describe the feature
On February 6, AWS announced the release of NodeJS puppeteer runtimes 6.2 & 5.2, and python selenium runtime 2.1, and announced that all non-deprecated older versions will be deprecated on March 8th. Today, we got an email from AWS saying that new lambda runtimes will be deployed on March 19th and that the changes will not be backwards compatible with current puppeteer versions so we have to upgrade our runtimes
Those versions do not exist in the latest CDK version, so we need them to be added so that we can update our runtimes, test and deploy to production before the cutoff time
Use Case
AWS will upgrade the lambda runtimes to a non-compatible version with the current puppeteer runtimes, which will break our synthetic canaries.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.128
Environment details (OS name and version, etc.)
MacOS 14