lambda layers builds are broker

[gauravthadani]

Hi team,
looking for some support on the lambda layers github action. we use these layers in our app, but the current builds are red and previous artifacts have expired.

link - https://github.com/aws-samples/amazon-textract-textractor/actions/workflows/lambda_layers.yml

the last error in the log is

 curl: (22) The requested URL returned error: 404
error: skipping https://rpmfind.net/linux/opensuse/distribution/leap/15.2/repo/oss/x86_64/libopenjpeg1-1.5.2-lp152.4.9.x86_64.rpm - transfer failed
Retrieving https://rpmfind.net/linux/opensuse/distribution/leap/15.2/repo/oss/x86_64/libopenjpeg1-1.5.2-lp152.4.9.x86_64.rpm
Error: Process completed with exit code 1.

any help will be great

[Belval]

Unfortunately this is a breaking change introduced by GitHub in actions/checkout and actions/upload-artifact. For now I will be disabling the lambda-layers for older version as we work on finding an alternative/solution.

On July 1st they updated the runtime to use Node20 which uses a more recent GLIBC version than lambda (except python 3.12), this causes the build to fail due to a version mismatch.

You can read the official announcement here: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/