10.0.0

[commonsensesoftware]

The official release for 10.0 is here! In addition to the changes in the preview releases, there are a few additional changes.

Features

All Platforms

• ApiVersionAttribute, MapToVersionAttribute, and AdvertiseApiVersionsAttribute all now have a constructor which can support the date format without being a string; for example, [ApiVersion(2026, 04, 01)]

ASP.NET Core OpenAPI

• XmlCommentsTransformer is now resolved via DI, which allows it to be re-registered with a user-defined file path
• Public types and members are now virtual for developer extensibility

Fixes

ASP.NET Core OpenAPI

• Fix comparison between entry and calling assembly (AddOpenApi does not find the XML documentation file when called from an extension library #1175)
• Ensure keyed services are registered with a lowercase key (Omitting GroupNameFormat causes Service Provider Exceptions #1176)
• Fix nested key service resolution (Clearer exceptions when accessing versioned OpenAPI documents that do not exist #1177)
• Implement IKeyedServiceProvider when injecting ApiVersion (10.0.0 Preview-2 - KeyedService does not work #1178)

Breaking Changes

ASP.NET Core OpenAPI

• OpenAPI documents use "enum": ["1.0"] instead of "default": "1.0"
  • This has a similar effect, but removes the free-form input when the value is bounded
  • When optional, the enum value can still be deleted/removed
  • Some UIs, such as Scalar, still provide a way to provide an enumerated value that isn't in the list

Release Notes

• Asp.Versioning.OData is being released as rc.1 because Microsoft.AspNetCore.OData is only at preview.2
• Asp.Versioning.OpenAPI is being released as rc.1 pending the outcome of API Proposal: Microsoft.AspNetCore.OpenAPI Not Extensible Due To Internal Types aspnetcore#66408
  • If the package can be released without requiring the explicit use of Reflection, that is the preference
  • No additional changes are planned unless bugs are reported

Feedback

Thanks to the contributors on this release whether it was code contributions or test driving the previews. Special thanks to @sander1095 for being a strong advocate and helping to bring even more visibility to the project.

---

This discussion was created from the release 10.0.0.

[Herve-M]

Looks like Asp.Versioning.OpenApi 10.0.0-rc.1 depends on Asp.Versioning.Mvc.ApiExplorer 10.0.0-rc.1 which wasn´t published yet?

[commonsensesoftware]

Ah ... thanks for pointing this out. This happened because I normally build and publish all in one go. This time, I had to do 2 runs. The rc.1 build implicitly chains the dependency (due to a project reference) to also be rc.1. You're correct that, in theory, there should be a 10.0.0-rc.1 for Asp.Versioning.Mvc.ApiExplorer. I'll work on seeing if I can get this updated. I'm not sure I can without publishing rc.2. If you explicitly add Asp.Versioning.Mvc.ApiExplorer as 10.0.0 that should work because 10.0.0 > 10.0.0-rc.1 by the semantic versioning rules. That should at least get you unblocked.