chore(deps): update gotenberg/gotenberg docker tag to v8.13.0 #175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.12.0
->8.13.0
Release Notes
gotenberg/gotenberg (gotenberg/gotenberg)
v8.13.0
: 8.13.0Compare Source
New Features
Select PDF Engines per Feature
You may now select PDF engines for each feature thanks to new flags:
--pdfengines-merge-engines
- Set the PDF engines and their order for the merge feature (default qpdf,pdfcpu,pdftk).--pdfengines-convert-engines
- Set the PDF engines and their order for the convert feature (default libreoffice-pdfengine).--pdfengines-read-metadata-engines
- Set the PDF engines and their order for the read metadata feature (default exiftool).--pdfengines-write-metadata-engines
- Set the PDF engines and their order the write metadata feature (default exiftool).--pdfengines-engines
is deprecated.Fail On Resource HTTP Status Codes (Chromium)
Like
failOnHttpStatusCodes
, the newfailOnResourceHttpStatusCodes
form field tells Gotenberg to return a 409 Conflict response if the HTTP status code from at least one resource is not acceptable.Resource Network Errors (Chromium)
The new form field
failOnResourceLoadingFailed
tells Gotenberg to return a 409 Conflict if Chromium encounters any of the following network errors while attempting to load a resource:net::ERR_CONNECTION_CLOSED
net::ERR_CONNECTION_RESET
net::ERR_CONNECTION_REFUSED
net::ERR_CONNECTION_ABORTED
net::ERR_CONNECTION_FAILED
net::ERR_NAME_NOT_RESOLVED
net::ERR_INTERNET_DISCONNECTED
net::ERR_ADDRESS_UNREACHABLE
net::ERR_BLOCKED_BY_CLIENT
net::ERR_BLOCKED_BY_RESPONSE
net::ERR_FILE_NOT_FOUND
Chore
130.0.6723.91
(except forarmhf
).You may now sponsor this open-source project. Thanks ❤️
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.