Update dependency @sparticuz/chromium to v123

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sparticuz/chromium	^103.0.0 -> ^123.0.0

---

Release Notes

Sparticuz/chromium (@​sparticuz/chromium)

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

• Update to 123.0.6312.0 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/241

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• https://github.com/puppeteer/puppeteer/pull/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 https://github.com/Sparticuz/chromium/pull/233
• Bump ncipollo/release-action from 1.13.0 to 1.14.0 by @​dependabot in https://github.com/Sparticuz/chromium/pull/228

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Update font layer description on README for v119.0.2+ by @​fukayatsu in https://github.com/Sparticuz/chromium/pull/213
• Update SAM example to v119 and fix readme link by @​davidjb in https://github.com/Sparticuz/chromium/pull/183
• Chromium 121 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/224

New Contributors

• @​fukayatsu made their first contribution in https://github.com/Sparticuz/chromium/pull/213

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Node 20 lambda support by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/187
• Updated Node 16 and 18 support by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/187

Special Thanks

• @​benasher44 for testing many times

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

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

New Contributors

• @​davidjb made their first contribution in https://github.com/Sparticuz/chromium/pull/178

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Bump actions/checkout from 3 to 4 by @​dependabot in https://github.com/Sparticuz/chromium/pull/156
• Bump ncipollo/release-action from 1.12.0 to 1.13.0 by @​dependabot in https://github.com/Sparticuz/chromium/pull/143
• Chromium 118 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/168

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Correct a few typos by @​Jamesllllllllll in https://github.com/Sparticuz/chromium/pull/149
• Chromium 117 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/161

New Contributors

• @​Jamesllllllllll made their first contribution in https://github.com/Sparticuz/chromium/pull/149

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Chromium 116 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/139

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Chromium 115 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/128

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Chromium 114 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/111

Bugfixes

• #​105

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• add netlify env check by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/98

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Bump @​types/node from 18.15.7 to 18.15.11 by @​dependabot in https://github.com/Sparticuz/chromium/pull/84
• Bump typescript from 5.0.2 to 5.0.3 by @​dependabot in https://github.com/Sparticuz/chromium/pull/83
• Bump typescript from 5.0.3 to 5.0.4 by @​dependabot in https://github.com/Sparticuz/chromium/pull/86
• Update to chromium 113 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/97

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Re-add --single-process to avoid chromium error by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/81

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Support for new Chromium 112 --headless=new flag, graphics stack enable/disable, lots of docs updates by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/76

New Features

• The default headless mode is changed to "new". This is a new feature of Chromium 112
  • https://developer.chrome.com/articles/new-headless/#try-out-the-new-headless
  • https://antoinevastel.com/bot%20detection/2023/02/19/new-headless-chrome.html
• The ability to disable WebGL, which can increase performance for Non-WebGL workloads.

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: https://github.com/Sparticuz/chromium/compare/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

• Bump typescript from 4.9.5 to 5.0.2 by @​dependabot in https://github.com/Sparticuz/chromium/pull/72
• Bump @​types/node from 18.14.0 to 18.15.3 by @​dependabot in https://github.com/Sparticuz/chromium/pull/71
• Chromium 112 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/74

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Add chromium-min example by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/59
• Add Chromium 111 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/61
• Bump @​types/node from 18.11.18 to 18.14.0 by @​dependabot in https://github.com/Sparticuz/chromium/pull/62
• Bump typescript from 4.9.4 to 4.9.5 by @​dependabot in https://github.com/Sparticuz/chromium/pull/47

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Build the typescript when building the layer manually by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/52
• Add examples by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/54
• Add follow-redirects by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/57

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Chromium 110 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/44

Full Changelog: https://github.com/Sparticuz/chromium/compare/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

• Cleanup by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/30
• feat: load chromium binary remote by @​aqaurius6666 in https://github.com/Sparticuz/chromium/pull/32
• Github actions by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/36
• Bump actions/setup-python from 3 to 4 by @​dependabot in https://github.com/Sparticuz/chromium/pull/37

Full Changelog: https://github.com/Sparticuz/chromium/compare/v109.0.1...v109.0.6

v109.0.5

Compare Source

v109.0.1

Compare Source

v109.0.0

Compare Source

v108.0.3

Compare Source

v108.0.2

Compare Source

v108.0.1

Compare Source

v108.0.0

Compare Source

v107.0.0

Compare Source

v106.0.2

Compare Source

v106.0.1

Compare Source

v106.0.0

Compare Source

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.