Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

⬆️ Update all (major) #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

⬆️ Update all (major) #6

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 7, 2022 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@sparticuz/chromium 108.0.3 -> 131.0.0 age adoption passing confidence dependencies major
@tsconfig/node14 (source) 1.0.3 -> 14.1.2 age adoption passing confidence devDependencies major
@types/node (source) 18.11.11 -> 22.9.0 age adoption passing confidence devDependencies major
@types/uuid (source) 9.0.0 -> 10.0.0 age adoption passing confidence devDependencies major
actions/checkout v3 -> v4 age adoption passing confidence action major
actions/setup-node v3 -> v4 age adoption passing confidence action major
get-stream 6.0.1 -> 9.0.1 age adoption passing confidence dependencies major
husky 8.0.2 -> 9.1.6 age adoption passing confidence devDependencies major
lint-staged 13.1.0 -> 15.2.10 age adoption passing confidence devDependencies major
mimetext 2.0.10 -> 3.0.24 age adoption passing confidence dependencies major
prettier (source) 2.8.0 -> 3.3.3 age adoption passing confidence devDependencies major
puppeteer (source) 19.3.0 -> 23.8.0 age adoption passing confidence devDependencies major
puppeteer-core (source) 19.3.0 -> 23.8.0 age adoption passing confidence dependencies major
typescript (source) 4.9.3 -> 5.6.3 age adoption passing confidence devDependencies major
uuid 9.0.0 -> 11.0.3 age adoption passing confidence dependencies major

Release Notes

Sparticuz/chromium (@​sparticuz/chromium)

v131.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v130.0.0...v131.0.0

v130.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v129.0.0...v130.0.0

v129.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v127.0.0...v129.0.0

v127.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v126.0.0...v127.0.0

v126.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v123.0.1...v126.0.0

v123.0.1

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v123.0.0...v123.0.1

v123.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v122.0.0...v123.0.0

v122.0.0

Compare Source

@​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

What's Changed

Full Changelog: Sparticuz/chromium@v121.0.0...v122.0.0

v121.0.0

Compare Source

@​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

New Contributors

Full Changelog: Sparticuz/chromium@v119.0.2...v121.0.0

v119.0.2

Compare Source

@​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

Special Thanks

Full Changelog: Sparticuz/chromium@v119.0.0...v119.0.2

v119.0.0

Compare Source

@​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

New Contributors

Full Changelog: Sparticuz/chromium@v118.0.0...v119.0.0

v118.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v117.0.0...v118.0.0

v117.0.0

Compare Source

@​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

New Contributors

Full Changelog: Sparticuz/chromium@v116.0.0...v117.0.0

v116.0.0

Compare Source

@​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

Full Changelog: Sparticuz/chromium@v115.0.0...v116.0.0

v115.0.0

Compare Source

@​sparticuz/chromium v115.0.0, @​sparticuz/chromium-min v115.0.0

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

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

Full Changelog: Sparticuz/chromium@v114.0.0...v115.0.0

v114.0.0

Compare Source

@​sparticuz/chromium v114.0.0, @​sparticuz/chromium-min v114.0.0

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

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

Bugfixes

Full Changelog: Sparticuz/chromium@v113.0.1...v114.0.0

v113.0.1

Compare Source

@​sparticuz/chromium v113.0.1, @​sparticuz/chromium-min v113.0.1

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

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

Full Changelog: Sparticuz/chromium@v113.0.0...v113.0.1

v113.0.0

Compare Source

@​sparticuz/chromium v113.0.0, @​sparticuz/chromium-min v113.0.0

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

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

  • Node 14 support has been dropped by Puppeteer, This package also drops Node 14 support.

What's Changed

Full Changelog: Sparticuz/chromium@v112.0.2...v113.0.0

v112.0.2

Compare Source

@​sparticuz/chromium v112.0.2, @​sparticuz/chromium-min v112.0.2

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

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

Full Changelog: Sparticuz/chromium@v112.0.1...v112.0.2

v112.0.1

Compare Source

@​sparticuz/chromium v112.0.1, @​sparticuz/chromium-min v112.0.1

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

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

Breaking

This is technically a breaking change because of the new Chromium headless version, however, no code changes are necessary

What's Changed

New Features

EDIT: NOTE! These must be called before launching chromium.

// Optional: If you'd like to use the legacy headless mode. "new" is the default.
chromium.setHeadlessMode = true;

// Optional: If you'd like to disable webgl, true is the default.
chromium.setGraphicsMode = false;

Full Changelog: Sparticuz/chromium@v112.0.0...v112.0.1

v112.0.0

Compare Source

@​sparticuz/chromium v112.0.0, @​sparticuz/chromium-min v112.0.0

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

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

Full Changelog: Sparticuz/chromium@v111.0.0...v112.0.0

v111.0.0

Compare Source

@​sparticuz/chromium v111.0.0, @​sparticuz/chromium-min v111.0.0

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

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

Full Changelog: Sparticuz/chromium@v110.0.1...v111.0.0

v110.0.1

Compare Source

@​sparticuz/chromium v110.0.1, @​sparticuz/chromium-min v110.0.1

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

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

Full Changelog: Sparticuz/chromium@v110.0.0...v110.0.1

v110.0.0

Compare Source

@​sparticuz/chromium v110.0.0, @​sparticuz/chromium-min v110.0.0

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

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

Full Changelog: Sparticuz/chromium@v109.0.6...v110.0.0

v109.0.6

Compare Source

@​sparticuz/chromium v109.0.6, @​sparticuz/chromium-min v109.0.6

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

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

The chromium-v109.0.6-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

Full Changelog: Sparticuz/chromium@v109.0.1...v109.0.6

v109.0.5

Compare Source

v109.0.1

Compare Source

v109.0.0

Compare Source

tsconfig/bases (@​tsconfig/node14)

v14.1.2

Compare Source

v14.1.1

Compare Source

actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

sindresorhus/get-stream (get-stream)

v9.0.1

Compare Source

  • Upgrade ReadableStream[Symbol.asyncIterator] ponyfill (#​128) df42674

v9.0.0

Compare Source

Breaking
Improvements

v8.0.1

Compare Source

Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate-major-all branch 3 times, most recently from bb3091d to d66f122 Compare January 18, 2023 04:08
@renovate renovate bot changed the title ⬆️ Update dependency @sparticuz/chromium to v109 ⬆️ Update dependency @sparticuz/chromium to v110 Jan 24, 2023
@renovate renovate bot changed the title ⬆️ Update dependency @sparticuz/chromium to v110 ⬆️ Update all (major) Mar 18, 2023
@renovate renovate bot force-pushed the renovate-major-all branch 3 times, most recently from 6811439 to 346b1ce Compare June 3, 2023 16:19
@renovate renovate bot force-pushed the renovate-major-all branch 7 times, most recently from 33616d3 to 05791b8 Compare June 16, 2023 10:08
@renovate renovate bot force-pushed the renovate-major-all branch 5 times, most recently from 803ebf5 to f120eef Compare June 28, 2023 07:05
@renovate renovate bot force-pushed the renovate-major-all branch 5 times, most recently from e508116 to 5a755e5 Compare July 5, 2023 13:21
@renovate renovate bot force-pushed the renovate-major-all branch 5 times, most recently from b79af1c to 561f72a Compare October 11, 2024 08:00
@renovate renovate bot force-pushed the renovate-major-all branch 6 times, most recently from ec3781d to d136e1d Compare October 23, 2024 09:32
@renovate renovate bot force-pushed the renovate-major-all branch 11 times, most recently from 1ae4231 to fd15f36 Compare October 31, 2024 19:11
@renovate renovate bot force-pushed the renovate-major-all branch 4 times, most recently from f2d008a to 4d42d7e Compare November 7, 2024 16:51
@renovate renovate bot force-pushed the renovate-major-all branch 2 times, most recently from 4e86988 to 7f4ae57 Compare November 13, 2024 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants