v131.0.0

@sparticuz/chromium v131.0.0, @sparticuz/chromium-min v131.0.0

The chromium-v131.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v131.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v131.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v131.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v131.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v131.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Chromium 131 by @Sparticuz in #317
• Support for Codebuilder lambda instances, thanks @tibbing

Full Changelog: v130.0.0...v131.0.0

v130.0.0

@sparticuz/chromium v130.0.0, @sparticuz/chromium-min v130.0.0

The chromium-v130.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v130.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v130.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v130.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v130.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v130.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Add chromium 130 by @Sparticuz in #310

Full Changelog: v129.0.0...v130.0.0

v129.0.0

@sparticuz/chromium v129.0.0, @sparticuz/chromium-min v129.0.0

The chromium-v129.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v129.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v129.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v129.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v129.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v129.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Chromium 129 by @Sparticuz in #306

Full Changelog: v127.0.0...v129.0.0

v127.0.0

@sparticuz/chromium v127.0.0, @sparticuz/chromium-min v127.0.0

The chromium-v127.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v127.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v127.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v127.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v127.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v127.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Chromium 127 by @Sparticuz in #290

Full Changelog: v126.0.0...v127.0.0

v126.0.0

@sparticuz/chromium v126.0.0, @sparticuz/chromium-min v126.0.0

The chromium-v126.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v126.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v126.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v126.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v126.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v126.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• update to chromium 126 by @Sparticuz in #284

Full Changelog: v123.0.1...v126.0.0

v123.0.1

@sparticuz/chromium v123.0.1, @sparticuz/chromium-min v123.0.1

The chromium-v123.0.1-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v123.0.1-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v123.0.1-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v123.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v123.0.1-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v123.0.1-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Misc Fixes by @Sparticuz in #252

Full Changelog: v123.0.0...v123.0.1

v123.0.0

@sparticuz/chromium v123.0.0, @sparticuz/chromium-min v123.0.0

The chromium-v123.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v123.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v123.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v123.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v123.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v123.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Update to 123.0.6312.0 by @Sparticuz in #241

Full Changelog: v122.0.0...v123.0.0

v122.0.0

@sparticuz/chromium v122.0.0, @sparticuz/chromium-min v122.0.0

The chromium-v122.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v122.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v122.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v122.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v122.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v122.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

Breaking Changes

• puppeteer/puppeteer#11815 Puppeteer changed the headless field values, should now be set to chrome-headless-shell for legacy use (Which is what @sparticuz/chromium is using). true is reserved for future use.

What's Changed

• Chromium 122 by @Sparticuz in #233
• Bump ncipollo/release-action from 1.13.0 to 1.14.0 by @dependabot in #228

Full Changelog: v121.0.0...v122.0.0

v121.0.0

@sparticuz/chromium v121.0.0, @sparticuz/chromium-min v121.0.0

The chromium-v121.0.0-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v121.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v121.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v121.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v121.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v121.0.0-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Update font layer description on README for v119.0.2+ by @fukayatsu in #213
• Update SAM example to v119 and fix readme link by @davidjb in #183
• Chromium 121 by @Sparticuz in #224

New Contributors

• @fukayatsu made their first contribution in #213

Full Changelog: v119.0.2...v121.0.0

v119.0.2

@sparticuz/chromium v119.0.2, @sparticuz/chromium-min v119.0.2

The chromium-v119.0.2-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v119.0.2-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v119.0.2-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v119.0.2" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v119.0.2-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v119.0.2-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

What's Changed

• Node 20 lambda support by @Sparticuz in #187
• Updated Node 16 and 18 support by @Sparticuz in #187

Special Thanks

• @benasher44 for testing many times

Full Changelog: v119.0.0...v119.0.2