Jonas

> Workaround for this using CloudFormation The workaround works, thanks! But of course it's a lot of code compared to "native" httpApi support.

As of now, we cannot migrate to sls v4 (which is still in **alpha**!) until Jul 15, 2024. Probably others also have to see if they get "approval" for the...

[Update from AWS](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy): > **Runtime deprecation for Node.js 16** > In response to customer feedback, AWS is **delaying the deprecation of the Node.js 16 runtime** until 9 months after the...

Thanks @wesyoung! But that would mean that [this](https://github.com/serverless/serverless/pull/12146#issuecomment-1716183178) is not true? (Would surprise me to be honest.) > However we can't just increment the runtime version. These custom resource handlers...

Related: - https://github.com/sidorares/node-mysql2/pull/2131 - https://github.com/sidorares/node-mysql2/issues/2172#issuecomment-1680802232

We also experienced a similar or the same issue with Serverless v3 (to be more precise: the fork from [oss-serverless/serverless](https://github.com/oss-serverless/serverless)) and `nodejs22.x`. Thanks to your description, I moved the S3...

Is this still planned? That would be a very useful feature, because currently I have to add the tracks to the queue via context menu and then reorder them there.