Repository navigation
build(deps): Bump QuestPDF and Swashbuckle.AspNetCore - #26
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
This was referenced 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
Bot
force-pushed
the
dependabot/nuget/src/NewVixSmart.Web/third-party-9c6bb86b27
branch
from
October 5, 2026 04:37
222ecfb to
821edba
Compare
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
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 2026.8.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)
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
anyOf,allOf,oneOfortype = nullby @ldeluigi in Change nullability handling for schemas with anyOf, allOf, oneOf or type = null domaindrivendev/Swashbuckle.AspNetCore#3976AddServeracross multiple documents by @RaphaelFakhri in Add coverage for AddServer across multiple documents domaindrivendev/Swashbuckle.AspNetCore#4115[EnumMember]by @RaphaelFakhri in Document that System.Text.Json ignores [EnumMember] domaindrivendev/Swashbuckle.AspNetCore#4127ConfigObject.AdditionalItemsby @RaphaelFakhri in Fix #3153: serialize custom values in the UI ConfigObject AdditionalItems domaindrivendev/Swashbuckle.AspNetCore#4132New 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
SOURCE_DATE_EPOCHby @martincostello in Set SOURCE_DATE_EPOCH domaindrivendev/Swashbuckle.AspNetCore#3997InvalidOperationExceptionif no route matches by @martincostello in Fix InvalidOperationException if no route matches domaindrivendev/Swashbuckle.AspNetCore#3999[MinLength]/[MaxLength]on dictionary properties tominProperties/maxPropertiesby @KitKeen in Map [MinLength]/[MaxLength] on dictionary properties to minProperties / maxProperties domaindrivendev/Swashbuckle.AspNetCore#3922ExposeSwaggerDocumentUrlsRoutebehaviour by @martincostello in Fix ExposeSwaggerDocumentUrlsRoute behaviour domaindrivendev/Swashbuckle.AspNetCore#4000NUGET_API_KEYby @martincostello in Use NUGET_API_KEY domaindrivendev/Swashbuckle.AspNetCore#4006New 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
MapSwaggerUIandMapReDocto support endpoint routing by @Strepto in Add MapSwaggerUI and MapReDoc to support endpoint routing domaindrivendev/Swashbuckle.AspNetCore#3822HEADrequests by @snebjorn in Support HEAD requests domaindrivendev/Swashbuckle.AspNetCore#3887IAsyncSwaggerProviderin CLItofilecommand by @bt-Knodel in Use IAsyncSwaggerProvider in CLI tofile command domaindrivendev/Swashbuckle.AspNetCore#3910New 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
"null"by @jgarciadelanoceda in Fix null examples being represented as the string null domaindrivendev/Swashbuckle.AspNetCore#3788Full 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
SchemaRepository.ReplaceSchemaIdby @bkoelman in Add public method SchemaRepository.ReplaceSchemaId domaindrivendev/Swashbuckle.AspNetCore#3708Bug Fixes
AllOfby @John-Paul-R in fix(SchemaGenerator): exclude inherited properties only when base add… domaindrivendev/Swashbuckle.AspNetCore#3692Miscellaneous
TryLookupByTypewith nullability hints by @martincostello in Annotate TryLookupByType for nullability domaindrivendev/Swashbuckle.AspNetCore#3719New 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
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:
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.6...v10.0.0
Commits viewable in compare view.