Repository navigation
chore: prepare Core.OpenApi 2.2.0 and Swashbuckle 1.2.1 - #17
Merged
Merged
Conversation
Core.OpenApi 2.2.0 (BREAKING): default problem schemas change to CoreProblemDetails and CoreValidationProblemDetails. Adds ValidationSchemaId and includes CoreProblemDetails in ProblemSchemaIds by default. Release notes describe how to restore the previous names. Swashbuckle 1.2.1: wildcard listen addresses (+, *, 0.0.0.0, [::]) are no longer registered as Local servers in Development. Depends on CoreSystem.OpenApi 2.1.0 until 2.2.0 is on nuget.org. Also corrects a stray statement in OpenApiRegistration.cs that broke the build, restores the ProducesOk/ProducesCreated/ProducesNoContent row in the Swashbuckle README, and documents ProducesConflictProblemAttribute in the Core README.
ValidationSchemaId now follows SchemaId unless set explicitly. While SchemaId keeps its default, the 400 response still uses CoreValidationProblemDetails. The patcher resolves the 400 schema from ValidationSchemaId when a definition does not declare its own. Core.OpenApi.Swashbuckle references the Core project when UseLocalProjectReferences is true, so local builds see the new property. CI still resolves CoreSystem.OpenApi from nuget until 2.2.0 is published.
coverlet 10.1.0 -> 10.1.1, xunit.v3 4.0.2 -> 4.0.3, Microsoft.AspNetCore.TestHost and Mvc.Testing for net10.0 10.0.13 -> 10.0.15. Lock files regenerated with the default package-based restore (no project references).
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.
📋 Description
Prepares the next releases of both packages:
CoreProblemDetailsandCoreValidationProblemDetails. AddsValidationSchemaId, andProblemSchemaIdsincludesCoreProblemDetailsby default. Release notes explain how to restoreProblemDetailsandValidationProblemDetails.+,*,0.0.0.0,[::]) are no longer added as Local servers in Development.OpenApiRegistration.csthat broke the build.ProducesOk/ProducesCreated/ProducesNoContentrow in the Swashbuckle README and documentsProducesConflictProblemAttributein the Core README.docs/OpenApi→docs/Swashbuckle,docs/Attributes.md) andmkdocs.ymlthat were already staged.Publish order: Core 2.2.0 first, then update the central pin in
Directory.Packages.propsfrom 2.1.0 to 2.2.0 and regenerate lock files, then Swashbuckle 1.2.1. Swashbuckle 1.2.1 currently builds against CoreSystem.OpenApi 2.1.0 because 2.2.0 is not yet on nuget.org.🎯 Type of Change
✨ What's New
✅ Checklist
dotnet build CoreSystem.OpenApi.slnx -c Releasesucceedsdotnet test): 168 passed, 0 failedREADME.mdanddocs/updated if public surface changedpackages.lock.jsonregenerated if dependencies changed (no dependency change in this PR; the central pin stays at 2.1.0 until Core 2.2.0 is published)📚 References
src/Core.OpenApi/Core.OpenApi.csproj,src/Core.OpenApi.Swashbuckle/Core.OpenApi.Swashbuckle.csproj