Update dependency @sparticuz/chromium to v131 #2559
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^130.0.0
->^131.0.0
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 codeThe
chromium-v131.0.0-pack.tar
file may be uploaded to any https endpoint and the remote location may be used as theinput
variable in thechromium.executablePath(input)
function.What's Changed
Full Changelog: Sparticuz/chromium@v130.0.0...v131.0.0
Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.