fix(deps): update dependency @sparticuz/chromium-min to v131

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sparticuz/chromium-min	^130.0.0 -> ^131.0.0

---

Release Notes

Sparticuz/chromium (@​sparticuz/chromium-min)

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

• Chromium 131 by @​Sparticuz in https://github.com/Sparticuz/chromium/pull/317
• Support for Codebuilder lambda instances, thanks @​tibbing

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

---

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 was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
capture-screenshots	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 13, 2024 7:18pm