build(deps): bump @sparticuz/chromium from 138.0.1 to 143.0.0 in /serverless

[dependabot]

Bumps @sparticuz/chromium from 138.0.1 to 143.0.0.

Release notes

Sourced from @​sparticuz/chromium's releases.

v143.0.0

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

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

bucketName="chromiumUploadBucket" && archType="x64" && \
aws s3 cp chromium-v143.0.0-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v143.0.0-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v143.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v143.0.0-layer.${archType}.zip" --compatible-runtimes "nodejs20.x" "nodejs22.x" --compatible-architectures $(if [ "$archType" = "x64" ]; then echo "x86_64"; else echo "$archType"; fi)

The chromium-v143.0.0-pack.ARCH.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.

Support this project's continued development by becoming a monthly sponsor on GitHub. Your contribution helps cover monthly maintenance costs and ensures ongoing improvements.

What's Changed

• fix example code in README.md by @​cognettings in Sparticuz/chromium#475
• Bump actions/checkout from 5 to 6 by @​dependabot[bot] in Sparticuz/chromium#473
• Bump actions/upload-artifact from 4 to 5 by @​dependabot[bot] in Sparticuz/chromium#469
• Bump actions/download-artifact from 5 to 6 by @​dependabot[bot] in Sparticuz/chromium#468
• Node 24 & Chromium 143 by @​Sparticuz in Sparticuz/chromium#476

New Contributors

• @​cognettings made their first contribution in Sparticuz/chromium#475

Full Changelog: Sparticuz/chromium@v141.0.0...v143.0.0

v141.0.0

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

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

bucketName="chromiumUploadBucket" && archType="x64" && \
aws s3 cp chromium-v141.0.0-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v141.0.0-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v141.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v141.0.0-layer.${archType}.zip" --compatible-runtimes "nodejs20.x" "nodejs22.x" --compatible-architectures $(if [ "$archType" = "x64" ]; then echo "x86_64"; else echo "$archType"; fi)

The chromium-v141.0.0-pack.ARCH.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.

Support this project's continued development by becoming a monthly sponsor on GitHub. Your contribution helps cover monthly maintenance costs and ensures ongoing improvements.

What's Changed

• Update the chromium version to 141.0.7382 by @​gauravrmazra in Sparticuz/chromium#447
• Update the Chromium version to 141 by @​Sparticuz in Sparticuz/chromium#454

New Contributors

• @​gauravrmazra made their first contribution in Sparticuz/chromium#447

Full Changelog: Sparticuz/chromium@v140.0.0...v141.0.0

v140.0.0

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

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

bucketName="chromiumUploadBucket" && archType="x64" && \
aws s3 cp chromium-v140.0.0-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v140.0.0-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v140.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v140.0.0-layer.${archType}.zip" --compatible-runtimes "nodejs20.x" "nodejs22.x" --compatible-architectures $(if [ "$archType" = "x64" ]; then echo "x86_64"; else echo "$archType"; fi)
</tr></table> 

... (truncated)

Commits

• 6c2f507 143.0.0
• c4bc1e8 Merge pull request #476 from Sparticuz/feature/chromium143+node24
• 317197f Pin python to 3.13 for now
• 8c2593c fix permissions
• ae3d9fa Chromium 143 arm64
• ed00ed4 Chromium 143 x64
• 3f04929 Node 24 support
• fcdbd58 Update lint
• 1ce7c79 Update deps
• d0419ee Merge pull request #468 from Sparticuz/dependabot/github_actions/actions/down...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[dependabot]

Superseded by #622.