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

v119.0.1-next.0

@sparticuz/chromium v119.0.1-next.0, @sparticuz/chromium-min v119.0.1-next.0

The chromium-v119.0.1-next.0-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.1-next.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v119.0.1-next.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v119.0.1-next.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v119.0.1-next.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v119.0.1-next.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.

Full Changelog: v119.0.0...v119.0.1-next.0

v119.0.0

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

The chromium-v119.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-v119.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v119.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v119.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v119.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v119.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

• Bump actions/setup-node from 3 to 4 by @dependabot in #171
• Bump @types/node from 18.18.6 to 18.18.7 by @dependabot in #170
• Add AWS SAM LayerVersion example by @davidjb in #178
• Bump @types/tar-fs from 2.0.3 to 2.0.4 by @dependabot in #181
• Bump @types/follow-redirects from 1.14.3 to 1.14.4 by @dependabot in #180
• Bump @types/node from 18.18.7 to 18.18.9 by @dependabot in #179
• add 119 by @Sparticuz in #182

New Contributors

• @davidjb made their first contribution in #178

Full Changelog: v118.0.0...v119.0.0

v118.0.0

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

The chromium-v118.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-v118.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v118.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v118.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v118.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v118.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

• Bump actions/checkout from 3 to 4 by @dependabot in #156
• Bump ncipollo/release-action from 1.12.0 to 1.13.0 by @dependabot in #143
• Chromium 118 by @Sparticuz in #168

Full Changelog: v117.0.0...v118.0.0

v117.0.0

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

The chromium-v117.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-v117.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v117.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v117.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v117.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v117.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

• Correct a few typos by @Jamesllllllllll in #149
• Chromium 117 by @Sparticuz in #161

New Contributors

• @Jamesllllllllll made their first contribution in #149

Full Changelog: v116.0.0...v117.0.0

v116.0.0

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

The chromium-v116.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-v116.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v116.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v116.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v116.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v116.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 116 by @Sparticuz in #139

Full Changelog: v115.0.0...v116.0.0