fix: bump @sparticuz/chromium from 110.0.1 to 113.0.1

[dependabot]

Bumps @sparticuz/chromium from 110.0.1 to 113.0.1.

Release notes

Sourced from @​sparticuz/chromium's releases.

v113.0.1

@​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 Sparticuz/chromium#98

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

v113.0.0

@​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 Sparticuz/chromium#84
• Bump typescript from 5.0.2 to 5.0.3 by @​dependabot in Sparticuz/chromium#83
• Bump typescript from 5.0.3 to 5.0.4 by @​dependabot in Sparticuz/chromium#86
• Update to chromium 113 by @​Sparticuz in Sparticuz/chromium#97

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

v112.0.2

@​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 Sparticuz/chromium#81

... (truncated)

Commits

• b8a406a 113.0.1
• b21fdac Merge pull request #98 from Sparticuz/fix/netlify
• 3b51330 Update deps
• 7c33343 add netlify env check
• b1810b4 113.0.0
• 2c2eeba Merge pull request #97 from Sparticuz/feature/chromium113
• ccf85f2 Merge branch 'master' into feature/chromium113
• c72041f change file permissions
• 71b254a remove node 14
• 0786301 Drop node 14 support
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)