Skip to content

build(deps): Bump QuestPDF and Swashbuckle.AspNetCore - #26

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/src/NewVixSmart.Web/third-party-9c6bb86b27
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/src/NewVixSmart.Web/third-party-9c6bb86b27

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 30, 2026 •

Copy link
Copy Markdown

Updated QuestPDF from 2026.8.0 to 2026.9.1.

Release notes

Sourced from QuestPDF's releases.

2026.9.1

  • Updated Skia to m154.
  • Updated qpdf to 12.4.1.
  • Fixed an issue where garbage collection could corrupt PDF tag attributes during concurrent PDF generation (found and fixed by @​Lurtz7 in Keep PDF/UA attribute strings alive until the document is closed (fixes stale-pointer corruption and crashes in document_close) QuestPDF/QuestPDF#1483),
  • Improved PDF/UA-1 compatibility when generating ZUGFeRD and Factur-X invoices.
  • Fixed an issue in the DocumentOperation API where DocumentAttachmentRelationship.Supplement was incorrectly mapped to /Alternative.
  • Improved handling of stream-writing exceptions during PDF generation.
  • The ShowInCompanion API now automatically starts the Companion App if it is not already running (requires Companion App 2026.9.0 or newer).
  • Improved exception messages related to Settings.ThrowOnMissingFontFamilies, Settings.ThrowOnMissingTextGlyphs, and Settings.UseSystemFonts.
  • Reduced connection time to the Companion App on Windows.
  • Added missing license files for dependencies.

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)

Commits viewable in compare view.

Updated Swashbuckle.AspNetCore from 9.0.6 to 10.3.0.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

10.3.0

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.3...v10.3.0

10.2.3

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.2...v10.2.3

10.2.2

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.1...v10.2.2

10.2.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.0...v10.2.1

10.2.0

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.7...v10.2.0

10.1.7

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.6...v10.1.7

10.1.6

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.5...v10.1.6

10.1.5

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.4...v10.1.5

10.1.4

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.3...v10.1.4

10.1.3

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.2...v10.1.3

10.1.2

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.1...v10.1.2

10.1.1

What's Changed

New Contributors

Full Changelog:

domaindrivendev/Swashbuckle.AspNetCore@v10.1.0...v10.1.1

10.1.0

What's Changed

New Features

Bug Fixes

Miscellaneous

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.0.1...v10.1.0

10.0.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.0.0...v10.0.1

10.0.0

Swashbuckle.AspNetCore v10.0.0

[!IMPORTANT]
This release contains major breaking changes.

Read our v10 migration guide for further information.

With this release, Swashbuckle.AspNetCore adds support for generating OpenAPI 3.1 documents and for ASP.NET Core 10.

Swashbuckle.AspNetCore v10 depends on OpenAPI.NET v2.3 which introduces many breaking changes to the public API surface. More information can be found in their OpenAPI.NET v2 Upgrade Guide.

To reduce the number of breaking behavioural changes in Swashbuckle.AspNetCore v10, generation of OpenAPI 3.1 documents is opt-in.
To generate OpenAPI 3.1 documents, change the OpenAPI version as shown in the code snippet below:

app.UseSwagger(options =>
{
    options.OpenApiVersion = OpenApiSpecVersion.OpenApi3_1;
});

[!TIP]
It is strongly recommended that you upgrade to Swashbuckle.AspNetCore v9.0.6 before upgrading to v10.

[!IMPORTANT]
Use of Swashbuckle.AspNetCore with the ASP.NET Core WithOpenApi() method is no longer supported.

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.6...v10.0.0

Commits viewable in compare view.

@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Sep 30, 2026
@dependabot
dependabot Bot requested a review from NewVixSmart as a code owner September 30, 2026 07:41
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code labels Sep 30, 2026
Bumps QuestPDF from 2026.8.0 to 2026.9.1
Bumps Swashbuckle.AspNetCore from 9.0.6 to 10.2.3

---
updated-dependencies:
- dependency-name: QuestPDF
  dependency-version: 2026.9.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: third-party
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 10.2.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: third-party
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps): Bump the third-party group with 2 updates build(deps): Bump QuestPDF and Swashbuckle.AspNetCore Oct 5, 2026
@dependabot
dependabot Bot force-pushed the dependabot/nuget/src/NewVixSmart.Web/third-party-9c6bb86b27 branch from 222ecfb to 821edba Compare October 5, 2026 04:37
@dependabot @github

dependabot Bot commented on behalf of github Oct 12, 2026

Copy link
Copy Markdown
Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants