Updated version to 2.4.0. #148
Conversation
| <PropertyGroup> | ||
| <MajorVersion>2</MajorVersion> | ||
| <MinorVersion>3</MinorVersion> | ||
| <MinorVersion>4</MinorVersion> |
There was a problem hiding this comment.
We should only update the base package version and release that first. Once Microsoft.FeatureManagement v2.4.0 is on NuGet, we can bump up the version of AspNetCore project and also update the base package reference at the same time.
There was a problem hiding this comment.
The AspNetCore project does not reference the base project by package version.
There was a problem hiding this comment.
With the current setup, both packages are built as v2.4.0 and the aspnet core package declares a reference to 2.4.0 of the base package.
There was a problem hiding this comment.
This is a little bit different than the setup in AppConfiguration-DotNetProvider which I believe has the setup it does for some historical reasons, but maybe we could even simplify that.
There was a problem hiding this comment.
Oh I see, in that case we don't need separate version upgrades because AspNetCore project has a reference to the base project directly.
For DotNetProvider, we need two different version upgrades because AspNetCore project references the latest base package from NuGet.
2 participants
Updated version to 2.4.0.