Skip to content

1.2.0
Compare
Choose a tag to compare
@commonsensesoftware commonsensesoftware released this 03 Jul 17:59
v1.2.0
a15fe09

This is quick, minor release, but with a significant reversion. The 1.1.0 release required ASP.NET Core users to add app.UseApiVersioning(); to their startup configurations. This was really easy to miss and a hung a lot of people up. Unfortunately, that was a required change to fix issues in 1.0.0 for some users and I had yet to find a good way to handle the scenario or fail explicitly when the configuration was missing by the time of release.

I'm happy to report for ASP.NET Core users that I've found a way to inject the behavior required by app.UseApiVersioning(); without actually making you call it. Apologies to early 1.1.x adopters who went through the pain of discovering this was needed, adding it, and now having to remove it. Ultimately, I feel this is the best decision for all users long term. Since current adoption of 1.1.x is only around 1% of 1.0.x, most people who upgrade will never see or deal with the related issues. I have subsequently updated all wiki topics and unlisted the 1.1.x NuGet packages so that users that upgrade will never encounter these issues.

Fixes

The following are fixes addressed in the current release

ASP.NET Web API

  • Improve automatically cloning of MediaTypeFormatter instances; affects API versioning by media type (#156)

ASP.NET Core

  • Address possible NullReferenceException building allowed HTTP methods
  • Update action for routes with overlapping route templates (#147 and #148)

Breaking Changes

The following are breaking changes in the current release

ASP.NET Core

  • Remove the need for and use of UseApiVersioning; affects >= 1.1.0-rc and < 1.2.0 only (#152)
Assets 2
Loading