starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[PR #5186] [MERGED] Bump Swashbuckle.AspNetCore.ReDoc from 5.6.3 to 6.0.2 #10418

New Issue
Closed
opened 2026-02-07 06:19:58 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 06:19:58 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/5186
Author: @dependabot[bot]
Created: 2/8/2021
Status: ✅ Merged
Merged: 2/8/2021
Merged by: @dkanada

Base: master ← Head: dependabot/nuget/Swashbuckle.AspNetCore.ReDoc-6.0.2

📝 Commits (1)

  • df121c1 Bump Swashbuckle.AspNetCore.ReDoc from 5.6.3 to 6.0.2

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 Jellyfin.Api/Jellyfin.Api.csproj (+1 -1)

📄 Description

Bumps Swashbuckle.AspNetCore.ReDoc from 5.6.3 to 6.0.2.

Release notes

Sourced from Swashbuckle.AspNetCore.ReDoc's releases.

v6.0.0

This release includes a number of small enhancements and bug fixes. See the following for a full list of issues addressed: https://github.com/domaindrivendev/Swashbuckle.AspNetCore/milestone/16?closed=1

Of note, these include:

  • include discriminator metadata in base schema if either UseOneOfForPolymorphism OR UseAllOfForInheritance are enabled
  • remove fragile logic around X-Forwarded-* headers in favor of MS's Forwarded Headers Middleware (*see breaking changes)
  • beta (opt-in) support for non-nullable reference types
  • enhancements to SwaggerSchemaAttribute incl. use on Enum types & ability to set Nullable flag explicitly
  • wrap generator exceptions to surface contextual info for troubleshooting
  • support JSON object/array syntax in XML tags
  • improved handling for enum default values to reflect serializer behavior more accurately
  • upgrade swagger-ui to 3.40.0

Breaking Changes

  • the obsolete settings DescribeAllEnumsAsStrings and DescribeStringEnumsInCamelCase are now fully removed
  • X-Forwarded-* headers are no longer honored within SB code - use MS's Forwarded Headers Middleware instead
Commits
  • 4331154 Revert breaking change to SchemaRepository.Schemas signature
  • 0b9b82b Update README.md
  • 52436b0 Update readme to reflect 6.0.1 release
  • cb61834 Upgrade swagger-ui to 3.42.0
  • 364006b Update readme for 6.0.0 release
  • c35dbc8 Add guidance for working with Reverse Proxies
  • 9c8f53b Merge pull request #1988 from domaindrivendev/support-nullable-via-swagger-sc...
  • 1d87942 Support setting Nullable via SwaggerSchemaAttribute
  • e9e7ee0 Merge pull request #1985 from domaindrivendev/fix-ci
  • 1172b62 Remove redundant build step that was causing issues
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/5186 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 2/8/2021 **Status:** ✅ Merged **Merged:** 2/8/2021 **Merged by:** [@dkanada](https://github.com/dkanada) **Base:** `master` ← **Head:** `dependabot/nuget/Swashbuckle.AspNetCore.ReDoc-6.0.2` --- ### 📝 Commits (1) - [`df121c1`](https://github.com/jellyfin/jellyfin/commit/df121c1516e4fa531904529397736e89ca41366c) Bump Swashbuckle.AspNetCore.ReDoc from 5.6.3 to 6.0.2 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `Jellyfin.Api/Jellyfin.Api.csproj` (+1 -1) </details> ### 📄 Description Bumps [Swashbuckle.AspNetCore.ReDoc](https://github.com/domaindrivendev/Swashbuckle.AspNetCore) from 5.6.3 to 6.0.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/releases">Swashbuckle.AspNetCore.ReDoc's releases</a>.</em></p> <blockquote> <h2>v6.0.0</h2> <p>This release includes a number of small enhancements and bug fixes. See the following for a full list of issues addressed: <a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/milestone/16?closed=1">https://github.com/domaindrivendev/Swashbuckle.AspNetCore/milestone/16?closed=1</a></p> <p><strong>Of note, these include:</strong></p> <ul> <li>include discriminator metadata in base schema if <em>either</em> UseOneOfForPolymorphism OR UseAllOfForInheritance are enabled</li> <li>remove fragile logic around X-Forwarded-* headers in favor of MS's Forwarded Headers Middleware (*see breaking changes)</li> <li>beta (opt-in) support for non-nullable reference types</li> <li>enhancements to SwaggerSchemaAttribute incl. use on Enum types &amp; ability to set Nullable flag explicitly</li> <li>wrap generator exceptions to surface contextual info for troubleshooting</li> <li>support JSON object/array syntax in XML <!-- raw HTML omitted --> tags</li> <li>improved handling for enum default values to reflect serializer behavior more accurately</li> <li>upgrade swagger-ui to 3.40.0</li> </ul> <p><strong>Breaking Changes</strong></p> <ul> <li>the <em>obsolete</em> settings <code>DescribeAllEnumsAsStrings</code> and <code>DescribeStringEnumsInCamelCase</code> are now fully removed</li> <li>X-Forwarded-* headers are no longer honored within SB code - use <a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore#working-with-reverse-proxies-and-load-balancers">MS's Forwarded Headers Middleware</a> instead</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/4331154ab9c4ff58da8cf7ff5f666d59fcd8c855"><code>4331154</code></a> Revert breaking change to SchemaRepository.Schemas signature</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/0b9b82b90c8cba3b84c00f7a4724cc90db159676"><code>0b9b82b</code></a> Update README.md</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/52436b0968d632041ee3e7c5d1ddf723148af67e"><code>52436b0</code></a> Update readme to reflect 6.0.1 release</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/cb618345937bdb819bf999810876dcdd0f5e28da"><code>cb61834</code></a> Upgrade swagger-ui to 3.42.0</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/364006b09be5e57cd0d552f11dc70d1cde2b0959"><code>364006b</code></a> Update readme for 6.0.0 release</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/c35dbc86e37648d12e3726b34d5fdbc059fbe039"><code>c35dbc8</code></a> Add guidance for working with Reverse Proxies</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/9c8f53b346eff41439ce86a9465f2b79a8b22aff"><code>9c8f53b</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/domaindrivendev/Swashbuckle.AspNetCore/issues/1988">#1988</a> from domaindrivendev/support-nullable-via-swagger-sc...</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/1d87942bd278a590e9621a269b7b303596d6decc"><code>1d87942</code></a> Support setting Nullable via SwaggerSchemaAttribute</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/e9e7ee06168e2036b943b559379eafa6816b4462"><code>e9e7ee0</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/domaindrivendev/Swashbuckle.AspNetCore/issues/1985">#1985</a> from domaindrivendev/fix-ci</li> <li><a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/commit/1172b62d45c22f0bf992a6a5b5d80c8a6445f476"><code>1172b62</code></a> Remove redundant build step that was causing issues</li> <li>Additional commits viewable in <a href="https://github.com/domaindrivendev/Swashbuckle.AspNetCore/compare/v5.6.3...v6.0.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=Swashbuckle.AspNetCore.ReDoc&package-manager=nuget&previous-version=5.6.3&new-version=6.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 06:19:58 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#10418
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?