Skip to content

Update dependency @sparticuz/chromium to v141 #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency @sparticuz/chromium to v141 #95

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 6, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@sparticuz/chromium ^103.0.0 -> ^141.0.0 age confidence

Release Notes

Sparticuz/chromium (@​sparticuz/chromium)

v141.0.0

Compare Source

@​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

New Contributors

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

v140.0.0

Compare Source

@​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)

The chromium-v140.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

Full Changelog: Sparticuz/chromium@v138.0.2...v140.0.0

v138.0.2

Compare Source

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

The chromium-v138.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-v138.0.2-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v138.0.2-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v138.0.2" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v138.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-v138.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.

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

v138.0.1

Compare Source

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

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

The chromium-v138.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.

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

v138.0.0

Compare Source

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

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

The chromium-v138.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-v138.0.0-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v138.0.0-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v138.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v138.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-v138.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.

What's Changed

Full Changelog: Sparticuz/chromium@v137.0.1...v138.0.0

v137.0.1

Compare Source

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

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

The chromium-v137.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.

  • Fixed NPM Package missing binaries

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

v137.0.0

Compare Source

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

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

!!! Do not blindly update to 137, read the following and make the needed code changes !!!

The chromium-v137.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-v137.0.0-layer.${archType}.zip "s3://${bucketName}/chromiumLayers/chromium-v137.0.0-layer.${archType}.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v137.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v137.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-v137.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.

Notable Changes

Lots has changed since the last public release of @​sparticuz/chromium 133.

Breaking Changes

  • Nearly all opinionated code has been removed. Users must now specify both the headless type as well as the viewport. A lot of args have also been removed.
Removed Args
  • ALL of Puppeteer's included args have been removed. This is replaced by using puppeteer.defaultArgs(). Playwright also includes a set of default args. The only args included are those required to run in serverless environments.
--allow-pre-commit-input
--disable-background-networking
--disable-background-timer-throttling
--disable-backgrounding-occluded-windows
--disable-breakpad
--disable-client-side-phishing-detection
--disable-component-extensions-with-background-pages
--disable-component-update
--disable-default-apps
--disable-dev-shm-usage
--disable-extensions
--disable-hang-monitor
--disable-ipc-flooding-protection
--disable-popup-blocking
--disable-prompt-on-repost
--disable-renderer-backgrounding
--disable-sync
--enable-automation
--enable-blink-features=IdleDetection
--export-tagged-pdf
--force-color-profile=srgb
--metrics-recording-only
--no-first-run
--password-store=basic
--use-mock-keychain
--disable-features="Translate,BackForwardCache,AcceptCHFrame,MediaRouter,OptimizationHints"
--enable-features="NetworkServiceInProcess2"
--disable-speech-api
--mute-audio
--hide-scrollbars
--window-size=1920,1080
Removed Opinionated Viewport

The User must now specify the viewport for Puppeteer. The following is a good default.

const viewport = {
  deviceScaleFactor: 1,
  hasTouch: false,
  height: 1080,
  isLandscape: true,
  isMobile: false,
  width: 1920,
}
Removed chromium.headless

The User must now specify the headless type for their library.

  • "shell" for Puppeteer
  • true for Playwright
arm64 Support

Finally! It's here! A layer and a pack are now built for arm64.

Dependencies

Dependencies (fonts and lib packs) are now built instead of manually curated files.

Summary of the PRs that make this release

Chromium 137 (#​359)
  • Upgraded bundled Chromium to version 137.
  • Enhanced documentation for "Extra Args" and contributions.
  • Updated build and test infrastructure:
    • Improved workflow scripts to better separate and handle x64 and arm64 builds, making artifact naming and handling explicit for both architectures.
    • Refined Makefile and Ansible scripts for multi-architecture support (archs now supports both x64 and arm64).
    • Improved test automation and artifact cleanup steps.
  • Code and integration test improvements:
    • Adjusted test event hashes and handler logic to match new Chromium and test requirements.
    • Refined TypeScript and handler implementations for clarity and maintainability.
Make an arm64 layer also (#​353)
  • Introduced explicit build and packaging for an ARM64 Lambda Layer.
  • Major refactoring to workflow scripts:
    • release.yml, test-arm.yml, and test-x64.yml updated to handle separate ARM64 and x64 artifacts.
    • Added and updated paths, artifact names, and packaging logic to support publishing both architectures.
    • Updates to Makefile and project files to ensure correct installation and packaging per architecture.
  • Moved binary artifacts to bin/x64 and bin/arm64 directories for clarity and separation.
  • Package configuration (package.json) updated to exclude unnecessary arch-specific files from wrong releases.
Major refactor, arm64 support, auto-gen dependencies (#​351)
  • Significant codebase refactor:
    • Dropped support for Node 16 and Node 18 (AL2), now requiring Node 20+.
    • Removed "opinionated" code: users must now explicitly specify viewport, headless mode, and args as needed.
      • Default viewport is no longer set; consumers should specify their own.
      • Headless mode is now set to 'shell' for Puppeteer and defaults to true for Playwright.
      • Args are now merged using Puppeteer's and Playwright's built-in logic.
    • All binary files (fonts.tar.br, al2023.tar.br) are now auto-generated.
  • Documentation overhaul:
    • README.md substantially revised for accuracy, clarity, and improved guidance.
    • Updated bug-report templates and references to reflect new Node.js and architecture support.
  • Improved Makefile and build/test scripts:
    • Test workflows and Makefile rules updated to handle only supported Node.js versions and architectures.
    • Reworked artifact naming and upload logic for clarity.
  • Removed legacy and redundant scripts and handlers; replaced with modern TypeScript/ESM implementations.

Note: This changelog is based on analysis of code changes in #​351, #​353, and #​359. For full details and diff, view the PR "Files changed" tab for each PR.

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

New Contributors

Full Changelog: Sparticuz/chromium@v133.0.0...v137.0.0

v133.0.0

Compare Source

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

The chromium-v133.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-v133.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v133.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v133.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v133.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v133.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

New Contributors

Full Changelog: Sparticuz/chromium@v132.0.0...v133.0.0

v132.0.0

Compare Source

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

The chromium-v132.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-v132.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v132.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v132.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v132.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v132.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

  • Update to chromium 132 by @​Sparticuz in #​335
  • The 'setHeadlessMode' option has been deprecated and will be removed in @​sparticuz/chromium@​133.0.1 chrome-headless-shell does not and will not be supporting the 'new' headless mode.

Full Changelog: Sparticuz/chromium@v131.0.1...v132.0.0

v131.0.1

Compare Source

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

The chromium-v131.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-v131.0.1-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v131.0.1-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v131.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v131.0.1-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v131.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

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

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

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

v130.0.0

Compare Source

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

The chromium-v130.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-v130.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v130.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v130.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v130.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v130.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

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

v129.0.0

Compare Source

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

The chromium-v129.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-v129.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v129.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v129.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v129.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v129.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

Full Changelog: Sparticuz/chromium@v127.0.0...v129.0.0

v127.0.0

Compare Source

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

The chromium-v127.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-v127.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v127.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v127.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v127.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v127.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

Full Changelog: Sparticuz/chromium@v126.0.0...v127.0.0

v126.0.0

Compare Source

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

The chromium-v126.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-v126.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v126.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v126.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v126.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v126.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

Full Changelog: Sparticuz/chromium@v123.0.1...v126.0.0

v123.0.1

Compare Source

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

The chromium-v123.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-v123.0.1-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v123.0.1-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v123.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v123.0.1-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v123.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

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

v123.0.0

Compare Source

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

The chromium-v123.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-v123.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v123.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v123.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v123.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v123.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

Full Changelog: Sparticuz/chromium@v122.0.0...v123.0.0

v122.0.0

Compare Source

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

The chromium-v122.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-v122.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v122.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v122.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v122.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v122.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 Changes

What's Changed

Full Changelog: Sparticuz/chromium@v121.0.0...v122.0.0

v121.0.0

Compare Source

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

The chromium-v121.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-v121.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v121.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v121.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v121.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v121.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

New Contributors

Full Changelog: Sparticuz/chromium@v119.0.2...v121.0.0

v119.0.2

Compare Source

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

The chromium-v119.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-v119.0.2-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v119.0.2-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v119.0.2" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v119.0.2-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v119.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

Special Thanks

Full Changelog: Sparticuz/chromium@v119.0.0...v119.0.2

v119.0.0

Compare Source

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

The chromium-v119.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-v119.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v119.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v119.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v119.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v119.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

New Contributors

Full Changelog: Sparticuz/chromium@v118.0.0...v119.0.0

v118.0.0

Compare Source

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

The chromium-v118.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-v118.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v118.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v118.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v118.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v118.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

Full Changelog: Sparticuz/chromium@v117.0.0...v118.0.0

v117.0.0

Compare Source

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

The chromium-v117.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-v117.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v117.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v117.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v117.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v117.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

New Contributors

Full Changelog: Sparticuz/chromium@v116.0.0...v117.0.0

v116.0.0

Compare Source

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

The chromium-v116.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-v116.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v116.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v116.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v116.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v116.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

Full Changelog: Sparticuz/chromium@v115.0.0...v116.0.0

v115.0.0

Compare Source

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

The chromium-v115.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-v115.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v115.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v115.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v115.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v115.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

Full Changelog: Sparticuz/chromium@v114.0.0...v115.0.0

v114.0.0

Compare Source

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

The chromium-v114.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-v114.0.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v114.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v114.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v114.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v114.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

Bugfixes

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

v113.0.1

Compare Source

@​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

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

v113.0.0

Compare Source

@​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

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

v112.0.2

Compare Source

@​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

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

v112.0.1

Compare Source

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

The chromium-v112.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-v112.0.1-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v112.0.1-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v112.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v112.0.1-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v112.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.

Breaking

This is technically a breaking change because of the new Chromium headless version, however, no code changes are necessary

What's Changed

  • Support for new Chromium 112 --headless=new flag, graphics stack enable/disable, lots of docs updates b

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants