Repository navigation
Bump QuestPDF from 2025.4.0 to 2026.9.1 - #16
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Owner
|
@dependabot rebase |
dependabot
Bot
force-pushed
the
dependabot/nuget/QuestPDF-2026.9.1
branch
from
October 29, 2026 00:52
cf6f0de to
c8ada37
Compare
--- updated-dependencies: - dependency-name: QuestPDF dependency-version: 2026.9.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/QuestPDF-2026.9.1
branch
from
October 31, 2026 21:30
c8ada37 to
1fe80b2
Compare
Contributor
Author
|
Superseded by #17. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated QuestPDF from 2025.4.0 to 2026.9.1.
Release notes
Sourced from QuestPDF's releases.
2026.9.1
DocumentOperationAPI whereDocumentAttachmentRelationship.Supplementwas incorrectly mapped to/Alternative.Settings.ThrowOnMissingFontFamilies,Settings.ThrowOnMissingTextGlyphs, andSettings.UseSystemFonts.2026.9.0
This release is dedicated to text handling improvements
QuestPDF 2026.9.0 improves font management to make document rendering more predictable across development machines, CI, containers, and cloud environments.
Fonts installed on the operating system vary between machines. A document that looks correct during development may use different fallback fonts, display placeholder glyphs, or lose text after deployment. To help catch these problems before a PDF reaches its recipient, QuestPDF now excludes system fonts by default and validates font availability and glyph coverage during document generation.
Upgrading to 2026.9.0
Deploy the required font files with your application and reference them by the family names stored in those files. Fonts in the application directory are registered automatically; you can also register them explicitly through
FontManager. UseFontManager.GetRegisteredFonts()to inspect the available family names.Please compare previous settings with the new defaults:
Also review the deployment and API changes below. Renamed APIs remain available under their previous names, marked as obsolete with compiler warnings.
Covering additional languages
QuestPDF includes the bundled Lato font, which covers Latin, Greek, and Cyrillic scripts. For other scripts, such as Chinese, Japanese, Korean, Arabic, Hebrew, Thai, or emoji, we recommend additionally deploying the free, open-source Google Noto font family, registering it with
FontManager, and configuring it as a font fallback in the default text style of the document.... (truncated)
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.2026.5.0
2026.2.4
2026.2.3
2026.2.2
2026.2.1
2026.2.0
2025.12.4
2025.12.3
2025.12.2
Fixes:
Improvements:
2025.12.1
2025.12.0
Features:
Future-proofing:
Bug fixes:
Maintenance:
2025.12.0-alpha4
2025.12.0-alpha3
2025.12.0-alpha2
2025.12.0-alpha1
2025.12.0-alpha0
We’re excited to share that this release adds initial support for semantic tagging and bookmarks! 🎉
For more details on both features, please see: QuestPDF/QuestPDF#1177
2025.7.4
2025.7.3
2025.7.2
2025.7.1
2025.7.0
2025.6.0-rc0
2025.5.1
2025.5.0
2025.4.4
Updated native dependencies:
2025.4.2
DocumentOperation.Decryptfeatre to remove encryption from PDF documents,DocumentOperation.RemoveRestrictionsfeature,Commits viewable in compare view.