Build(deps): bump @sparticuz/chromium from 119.0.2 to 127.0.0 in /services/pdfx

[dependabot]

Bumps @sparticuz/chromium from 119.0.2 to 127.0.0.

Release notes

Sourced from @​sparticuz/chromium's releases.

v127.0.0

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

• Chromium 127 by @​Sparticuz in Sparticuz/chromium#290

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

v126.0.0

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

• update to chromium 126 by @​Sparticuz in Sparticuz/chromium#284

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

v123.0.1

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

• Misc Fixes by @​Sparticuz in Sparticuz/chromium#252

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

v123.0.0

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

... (truncated)

Commits

• 517b6c4 127.0.0
• f9f32ca Merge pull request #290 from Sparticuz/chromium/127
• 2f7267d Update deps
• b580ec7 Chromium 127
• 5861327 Puppeteer updates for tests
• 8028819 126.0.0
• 995bc5a Merge pull request #284 from Sparticuz/chromium/126
• c51ae58 don't disable the graphics stack https://github.com/Sparticuz/chromium/issues...
• 2c715c4 update to chromium 126
• 2bcd54a ignore internal docker folder
• 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)