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

[dependabot]

Bumps @sparticuz/chromium from 138.0.1 to 147.0.2.

Release notes

Sourced from @​sparticuz/chromium's releases.

v147.0.2

@​sparticuz/chromium v147.0.2, @​sparticuz/chromium-min v147.0.2

The chromium-v147.0.2-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-v147.0.2-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v147.0.2-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v147.0.2" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v147.0.2-layer.${archType}.zip" --compatible-runtimes "nodejs20.x" "nodejs22.x" --compatible-architectures $(if [ "$archType" = "x64" ]; then echo "x86_64"; else echo "$archType"; fi)

The chromium-v147.0.2-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: workflow improvements for PR label state and VR comparison by @​Sparticuz in Sparticuz/chromium#501
• refactor: migrate from tsup to tsdown by @​Sparticuz in Sparticuz/chromium#500

Full Changelog: Sparticuz/chromium@v147.0.1...v147.0.2

v147.0.1

@​sparticuz/chromium v147.0.1, @​sparticuz/chromium-min v147.0.1

The chromium-v147.0.1-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-v147.0.1-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v147.0.1-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v147.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v147.0.1-layer.${archType}.zip" --compatible-runtimes "nodejs20.x" "nodejs22.x" "nodejs24.x" --compatible-architectures $(if [ "$archType" = "x64" ]; then echo "x86_64"; else echo "$archType"; fi)

The chromium-v147.0.1-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.

Breaking Changes

• Minimum Node.js version raised to 22.17.0 — required for stable native fetch and Readable.fromWeb() stream interop, which replace the follow-redirects dependency. Node 20 reaches EOL in October 2026, and even earlier on Lambda. (The package also most likely still works with node 20)

Changes

• Removed follow-redirects dependency — HTTP downloads now use Node's built-in fetch with Readable.fromWeb() for stream piping. Download timeout set to 300s for large files.
• Dual ESM/CJS builds via tsup — replaced tsc build with tsup bundler. CJS consumers get a proper CommonJS build at build/cjs/index.cjs

Infrastructure

• Replaced Ansible build system with EC2 user-data architecture — builds are now fire-and-forget: a GitHub Actions workflow launches a spot EC2 instance with a self-contained build script. The instance builds Chromium, uploads binaries to S3, and calls back to GitHub when done.
• Visual regression testing — PRs automatically get screenshot comparisons (example.com + WebGL) across x64 and arm64, with cross-architecture diff reporting
• Unified test workflow — single test.yml replaces separate test-x64.yml and test-arm.yml, with CJS test matrix

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

v147.0.0

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

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

</tr></table> 

... (truncated)

Commits

• 6ebbf67 147.0.2
• 5be3168 Merge pull request #500 from Sparticuz/feat/tsdown-migration
• eebf677 Merge pull request #501 from Sparticuz/fix/workflow-improvements
• a2a4726 fix: always output baseline revision in workflow even when S3 screenshots are...
• fa7903e fix: workflow improvements for PR label state and VR comparison
• 5ee1d3f refactor: migrate from tsup to tsdown
• cba626c fix: update ARM support information in README
• b3fd674 147.0.1
• 5301928 fix: update package size badge in README
• 4f25d0f fix: replace RELEASE_TOKEN with AUTOMATION_TOKEN in workflows and documentation
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​sparticuz/chromium since your current version.

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 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 #702.