Bug: Breaking change on sam 1.110 with NodeJs14

[atresca-globant]

Description:

Our Codebuild started failing 3 hours ago with the new sam version 1.110. Was working fine with version 1.109. we will migrate to Node20 but we are not there yet.

Throws this error:

Error: 'nodejs14.x' does not have a supported builder

314 | Traceback:
315 | File "/root/.pyenv/versions/3.9.17/lib/python3.9/site-packages/click/core.py", line 1078, in main

Steps to reproduce:

Observed result:

Expected result:

Run the sam build correctly with Nodejs 14

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

1. OS: Linux
2. sam --version: 1.110
3. AWS region: us-east-1b

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

Add --debug flag to command you are running

[lucashuy]

Hi, Lambda no longer supports updates to Node.js 14 based functions (https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy), which is why SAM CLI has removed support for this runtime with this latest version. While this is technically a breaking change, this is following the guidance from Lambda and migrating to a newer supported runtime should be the path forward.

[hnnasit]

Closing this issue as this is expected behavior due to runtime deprecation.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.