Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/8.0] Update Swashbuckle.AspNetCore to 6.6.2 #56266

Merged
merged 2 commits into from
Aug 8, 2024

Conversation

martincostello
Copy link
Member

@martincostello martincostello commented Jun 17, 2024

Description

Update Swashbuckle.AspNetCore in .NET 8 templates to a version that has built-in support for .NET 8 so users creating applications from the template get a better experience when creating new applications targeting .NET 8.

Customer Impact

Development on the Swashbuckle.AspNetCore repo has restarted after a haitus and Swashbuckle.AspNetCore 6.6.2 is the first release following this hiatus. The most impactful change here is that this release updates Swashbuckle to target the net8.0 TFM and fixes some long-standing bugs in the library.

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

6.6.2 has already been independently consumed by developers in their own APIs. This change updates the templates to in .NET 8 to use this version.

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

Update Swashbuckle.AspNetCore to a version that has built-in support for .NET 8.
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jun 17, 2024
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Jun 17, 2024
@dotnet-policy-service dotnet-policy-service bot added this to the 8.0.x milestone Jun 17, 2024
@captainsafia
Copy link
Member

@martincostello Thanks for opening this PR!

It looks like there is one "breaking" change here that affects the Grpc + Swagger integration (cc: @JamesNK). It seems that the descriptions that Swashbuckle produces for status codes might've changed? If that was intentional, I think we can update the tests and be fine.

@martincostello
Copy link
Member Author

If it's the change I'm thinking of, we made some changes in domaindrivendev/Swashbuckle.AspNetCore#2872 to align better with the RFC and add some missing entries.

If that fits with what's failing I can update the PR tomorrow to account for that.

@captainsafia
Copy link
Member

If it's the change I'm thinking of, we made some changes in domaindrivendev/Swashbuckle.AspNetCore#2872 to align better with the RFC and add some missing entries.

If that fits with what's failing I can update the PR tomorrow to account for that.

Yep, that appears to be what's happening in Microsoft.AspNetCore.Grpc.Swagger.Tests. You should be able to repro this failure locally as well.

Update expected description.
See domaindrivendev/Swashbuckle.AspNetCore#2872.
@martincostello
Copy link
Member Author

@captainsafia Fixed the test - the e2e component test failures seem unrelated and are affecting other PRs.

@captainsafia
Copy link
Member

@martincostello Thanks! And yes -- we're not blocking merging PRs to release/8.0 on the buggy components-e2e tests. I'll hold this PR until the 8.0 branch is open for merging.

@JamesNK JamesNK changed the title Update Swashbuckle.AspNetCore to 6.6.2 [release/8.0] Update Swashbuckle.AspNetCore to 6.6.2 Jun 19, 2024
@wtgodbe
Copy link
Member

wtgodbe commented Jul 2, 2024

@captainsafia is this good to go?

@captainsafia
Copy link
Member

@wtgodbe Is release/8.0 open for servicing? I'll need to email tactics for approval on this one.

@wtgodbe
Copy link
Member

wtgodbe commented Jul 2, 2024

Is release/8.0 open for servicing? I'll need to email tactics for approval on this one.

Yep!

@cremor
Copy link
Contributor

cremor commented Aug 1, 2024

I'll need to email tactics for approval on this one.

Any news on that @captainsafia?

@captainsafia
Copy link
Member

@cremor Argh -- dropped the ball on this. I'll try to get this in for the next servicing release.

@wtgodbe wtgodbe marked this pull request as ready for review August 1, 2024 15:49
@wtgodbe
Copy link
Member

wtgodbe commented Aug 1, 2024

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@captainsafia captainsafia added the Servicing-consider Shiproom approval is required for the issue label Aug 1, 2024
@rbhanda rbhanda added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Aug 6, 2024
@rbhanda rbhanda removed this from the 8.0.x milestone Aug 6, 2024
@rbhanda rbhanda added this to the 8.0.9 milestone Aug 6, 2024
@wtgodbe wtgodbe merged commit 6ee87a3 into dotnet:release/8.0 Aug 8, 2024
25 checks passed
@dotnet-policy-service dotnet-policy-service bot modified the milestone: 8.0.9 Aug 8, 2024
@martincostello martincostello deleted the patch-1 branch August 8, 2024 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework community-contribution Indicates that the PR has been added by a community member Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants