deps(fuzz): Bump QuestPDF from 2026.5.0 to 2026.8.0 - #210
dependabot[bot] wants to merge 2 commits into
Conversation
--- updated-dependencies: - dependency-name: QuestPDF dependency-version: 2026.8.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Not merging this one for now. QuestPDF stays pinned at 2026.5.0 per #77: the 2026.6.0 recovery-code PDF breakage was never reproduced on arm64/musl, and the recovery-PDF path was just stabilized in v2.6.1. #214 took every other bump but deliberately held this pin. We'll revisit 2026.8.0 once the recovery-code PDF is verified on arm64/musl. Closing for now. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Updated QuestPDF from 2026.5.0 to 2026.8.0.
Release notes
Sourced from QuestPDF's releases.
2026.8.0
🚀 This release is dedicated to performance, parallelism, and use of available resources. 🚀
Documents render faster, allocate a fraction of the memory they used to, and scale across all available CPU cores. No code changes are required — existing documents benefit simply by upgrading the package.
The numbers below were measured on a MacBook Pro M5 (18-core CPU), using the invoice document from the Getting Started tutorial, across various levels of parallelism, over a sample of 5,000 documents.
✨ Other improvements:
XPS generation has been removed. The format was supported only on Windows, had several rendering issues that could not be reliably resolved, and had negligible adoption. The GenerateXps and GenerateXpsAndShow methods are still present, but calling them now results in a compilation error, and code compiled against an earlier version throws an exception at runtime. Please use PDF generation instead.
2026.7.3
ImageGenerationSettings.UseTransparentBackground(applies only to formats supporting transparency: PNG and WEBP)./BBoxattribute, improving PDF/UA-1 compliance with validators that require it.GeneratePdfAndShowandGenerateXpsAndShowmethods.AsSemanticHorizontalHeaderin favor ofSemanticHorizontalHeaderfor API naming consistency.RotateLeftandRotateRightin favor ofRotateLayoutCounterclockwiseandRotateLayoutClockwise, which better describe what these methods do.2026.7.2
/ActualTexttag. This improves text selection, copying, extraction, and screen-reader accessibility. Ligatures remain disabled by default.AllowModificationpermission inDocumentOperationswhen encrypting PDF documents with 128-bit or 256-bit keys.DocumentOperationsAPI.2026.7.1
Improved performance
PDF generation is now significantly faster. The Skia native dependency has been recompiled with speed-oriented optimizations (favoring performance over binary size) and with SIMD instructions enabled.
The impact depends on document content and platform. For example, generating image-heavy documents that require image rescaling can be several times faster on Windows x64 🎉
Note: this change slightly increases the size of the native dependency by around 20%.
Continuous performance monitoring
We have also built a solid foundation for measuring library performance going forward. A new GitHub Actions workflow benchmarks QuestPDF across all supported operating systems, processor architectures, and .NET releases.
This infrastructure helps us ensure that performance remains stable and consistent across all platforms, and allows us to detect regressions early — before they ever reach a release.
2026.7.0
2026.6.1
2026.6.0
TranslateX/TranslateYmethods toOffsetX/OffsetYto improve discoverability.hrefattribute instead ofxlink:href.#RGBAand#RRGGBBAAcolor formats.transparentnamed color.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)