feat: add support for nodejs22.x runtime

[bchew]

Description

Add support for Node.js 22 runtime

Motivation and Context

AWS Lambda now supports Node.js 22:

• https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html
• https://aws.amazon.com/blogs/compute/node-js-22-runtime-now-available-in-aws-lambda/

Related PR in Serverless Framework: serverless/serverless#12916

How Has This Been Tested?

Screenshots (if appropriate):

[throrin19]

It is possible to made it for serverless-offline 13 and 14 ? Not only serverless-offline 14 ?

[alexw23]

Currently a blocker for us, looking forward to the patch.

[bchew]

It is possible to made it for serverless-offline 13 and 14 ? Not only serverless-offline 14 ?

Correct me if I'm wrong but serverless framework v3 does not support node 22 currently (serverless/serverless#12922), and serverless-offline 13 has a peer dep of serverless v3

[throrin19]

@bchew No worries with version 3 of serverless: I've been able to publish my lambdas in node22.x on AWS but I can't manage it locally with serverless-offline.

[alexw23]

@throrin19 I wasn't game enough to push without testing yet, so got stuck at not being able to launch locally.

Edit: actually, looking again it wasn't a failure, just a warning (on 13.3.4):

Warning: Invalid configuration encountered
  at 'provider.runtime': must be equal to one of the allowed values [dotnet6, go1.x, java17, java11, java8, java8.al2, nodejs14.x, nodejs16.x, nodejs18.x, nodejs20.x, provided, provided.al2, provided.al2023, python3.7, python3.8, python3.9, python3.10, python3.11, ruby2.7, ruby3.2]

[throrin19]

@alexw23 I understand, I revert the runtime until it is ready here.

After test yes the message is a warning but the offline lambda is not executed

[bchew]

Created a PR to v13 branch: #1838

[DorianMazur]

Amazing work, thanks!

[bchew]

@DorianMazur seems like all the tests are failing due to serverless v4 enforcing logins:

✖ Error: You must sign in or use a license key with Serverless Framework V.4 and later versions. Please use "serverless login".
    at Authentication.getAuthenticatedData (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:686:10535)
    at async Authentication.resolverAuthenticate (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:688:20566)
    at async _Meta.authenticate (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:696:12102)
    at async _Meta.authenticateAndResolve (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:696:11523)
    at async route (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:1010:14685)
    at async Object.run2 [as run] (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:1010:15173)
    at async run3 (file:///home/runner/.serverless/releases/4.4.13/package/dist/sf-core.js:1010:16435)

I assume a login is required to set access keys for GitHub Actions CI? #1835 has also the same failures in tests

[DorianMazur]

Yes, I am waiting for @dherault to respond. We need to find a way to run tests. They are failing because GitHub Secrets are not accessible in PR forks.

[dherault]

@DorianMazur What should I do?

[DorianMazur]

@dherault I messaged you elsewhere, but I'll copy it here:

If I understand it correctly, then we can enable "Send secrets to workflows from fork pull requests". The SERVERLESS_ACCESS_KEY isn’t a highly sensitive secret. I just created a free account on Serverless and generated this auth key, so there’s nothing to worry about. We can also configure it to always require approval for workflows on PRs- "Require approval for all outside collaborators".

[dherault]

I cannot seem to find this option, like it says it's only available to private repos.

The other one is already set.

[DorianMazur]

Okay @dherault
I have a better and safer idea. Please check out> #1840

[alexw23]

Is it not possible to just add the ACCESS_KEY to your forked repo for now? At least then we can get this PR through?

[edwinparejas]

The current version of serverless-offline 14.3.4 does not have support for nodejs22.x. When will you release a new version that supports nodejs22.x?

[DorianMazur]

@edwinparejas Yes, this weekend.