Replies: 1 comment 4 replies
-
The patch version of individual package isn't the same of shared framework. If there's no update to a package, its version won't be changed. To get the corresponding shared framework release (source tag), the simplest way is to inspect the release date. For example Extensions.Options 8.0.2 was released at Feb 13, so it belongs to 8.0.2 tag at Feb 13. It's just a coincidence for the numbers to be same.
You can check the git history of the library from the corresponding tag. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm in the process of simplifying some of our dependencies here in a large solution that was migrated from legacy
csproj
to the new SDK-stylecsproj
recently.I came across a case where we have the following library version that I was contemplating downgrading for simplicity:
Microsoft.Extensions.Options
v8.0.2
I wanted to see what the changes were between
v8.0.0
andv8.0.2
to see whether downgrading would be acceptable but I couldn't find this information anywhere.I started looking here in the
.NET 8.0.2
release:But none of the links or references seem to point to actual specific changes in that library, it is only listed as participating in the release.
I also didn't find any
CHANGELOG.md
document in the library folder itself, which is another common place to store changes on a per-project basis.Where can I find release notes for
Microsoft.Extensions.Options
and otherMicrosoft.Extensions.*
libraries? Are they actually available somewhere? If not, what is the best alternative method to check the differences between versions?Beta Was this translation helpful? Give feedback.
All reactions