Bug: Sam validate does not notice Node.js V22

[jalpp]

Description:

when creating a new sam project, Node.js v22 is given an option 11 which I created the project with, but after I have it and run SAM validate, the validation fails

Steps to reproduce:

• create a new project with SAM node.js V22
• run sam Validate and validation fails, probably because I'm on older SAM CLI version, but still even than sam validation should say update SAM rather than that bug.
  (I'm on 1.131.0 installed)

Observed result:

[[E3030: Check if properties have a valid value] ('nodejs22.x' is not one of ['dotnet6', 'dotnet8', 'dotnetcore1.0', 'dotnetcore2.0', 'dotnetcore2.1', 'dotnetcore3.1', 'go1.x', 'java11', 'java17', 'java21', 'java8', 'java8.al2', 'nodejs', 'nodejs10.x', 'nodejs12.x', 'nodejs14.x', 'nodejs16.x', 'nodejs18.x', 'nodejs20.x', 'nodejs4.3', 'nodejs4.3-edge', 'nodejs6.10', 'nodejs8.10', 'provided', 'provided.al2', 'provided.al2023', 'python2.7', 'python3.10', 'python3.11', 'python3.12', 'python3.13', 'python3.6', 'python3.7', 'python3.8', 'python3.9', 'ruby2.5', 'ruby2.7', 'ruby3.2', 'ruby3.3']) matched 14] Error: Linting failed. At least one linting rule was matched to the provided template.

Expected result:

SAM should tell me to either update my SAM, or it should not show Node.js v22 when picking the project in sam init

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS:
   Windows
2. sam --version:
   (I'm on 1.131.0 installed)
3. AWS region:

# Paste the output of `sam --info` here

Add --debug flag to command you are running

[valerena]

Hi. Thanks for the detailed report. This issues comes from cfn-lint package. We recently updated to a newer version of this package (#7895, #7902), so the next version of SAM CLI will have this runtime correctly checked. The next release should be later this week or the next.