chore(deps): Bump Microsoft.OpenApi and QuestPDF

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Updated Microsoft.OpenApi from 2.12.0 to 2.12.2.

Release notes

Sourced from Microsoft.OpenApi's releases.

2.12.2

2.12.2 (2026-08-20)

Bug Fixes

• duplicate schema example when serializing to v2 (#​3046) (a6366be)

2.12.1

2.12.1 (2026-08-19)

Bug Fixes

• circular ref guard (#​3033) (#​3039) (406e6fd)
• harden yaml parsing (#​3034) (fdc5718)

Commits viewable in compare view.

Updated QuestPDF from 2026.7.3 to 2026.9.0.

Release notes

Sourced from QuestPDF's releases.

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. Use FontManager.GetRegisteredFonts() to inspect the available family names.

Please compare previous settings with the new defaults:

// previous behavior:
QuestPDF.Settings.UseSystemFonts = true;
QuestPDF.Settings.ThrowOnMissingFontFamilies = false;
QuestPDF.Settings.ThrowOnMissingTextGlyphs = false;
QuestPDF.Settings.EnableDetailedLayoutErrors = false;

// current behavior:
QuestPDF.Settings.UseSystemFonts = false;
QuestPDF.Settings.ThrowOnMissingFontFamilies = true;
QuestPDF.Settings.ThrowOnMissingTextGlyphs = true;
QuestPDF.Settings.EnableDetailedLayoutErrors = true;

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.

// at application startup
FontManager.RegisterFontsFromDirectory("Fonts/Noto");

// in the document
Document.Create(document => 
{
    document.Page(page => 
    {
        page.DefaultTextStyle(style => style.FontFamily("Lato", "Noto Sans", "Noto Sans CJK SC", "Noto Emoji"));
    });
});

⚠️ Breaking changes

... (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.

• Reduced allocated memory amount and allocated object count by 85%.
• Improved single-threaded performance by around 15%.
• Substantially improved parallel scaling: throughput previously peaked at 4 threads and flattened beyond that, and now scales with available CPU cores — with around 4x better scaling.
• Improved performance and scalability for text-heavy documents.
• Improved cache usage (mainly for fonts) and significantly reduced locking.

✨ Other improvements:

• Added support for soft hyphens: the library does not hyphenate text automatically, but soft hyphen characters (U+00AD) are now correctly interpreted as optional break points and rendered as hyphens when a line breaks.
• Added the TextStyle.BreakAnywhere API, which allows a text span to break between any two characters, not only at word boundaries such as spaces or hyphens. Useful for content without natural break points, e.g. long URLs, identifiers, hashes, or file paths.
• Improved the visual position of the underline and double underline text decorations.
• Improved reliability of the Companion App integration: document previews are now refreshed from a consistent snapshot, and rendered pages are transferred more efficiently.
• Increased the zlib compression level used for PDF generation from 1 to 3, which produces significantly smaller files (for text-heavy documents) with a minimal increase in generation time.
• Updated the Skia native dependency to version m152.

⚠️ Breaking change

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.

Commits viewable in compare view.

[cnlarry]

关闭：本 PR 的两项都已过时或无需。QuestPDF 提的是 2026.9.0，而 main 上已经是 2026.9.1（PR #12 升级并适配了 2026.9 起取消「自定义名注册字体」的改动），合进来反而会降版本；Microsoft.OpenApi 2.12.0 到 2.12.2 是补丁级、本身没问题，但它与 QuestPDF 打在同一组里，下一次调度会单独重提，届时可直接合（3.x 仍受上游 Microsoft.AspNetCore.OpenApi 的 < 3.0.0 约束，已按 semver-major 挡在 dependabot.yml 里）。后端作业在这两个 PR 上失败的原因正是 QuestPDF 2026.9.0 的过时 API，该问题已由 #12 解决。

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml