-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can I see what issues are fixed in a release? #28000
Comments
@mattfrear all fixed issues are referenced by their Github milestone - here are all the milestones for released versions. For example, here are the issues fixed for 6.0.4. As 6.0.5 has just been released, its milestone hasn't yet been updated (/cc @AndriySvyryd we need to reassign the appropriate issues from 6.0.x). |
Thanks @roji. Looking forward to seeing the 6.0.5 milestone when it is updated. Perhaps your release process should change so that the milestone is updated before or when the NuGet is released? I still suggest that a Changelog would be easier to find and is somewhat of a standard (maybe?). PS. finally found #27600 which is the root cause I was looking for. |
You can find changelogs in the Releases but again 6.0.5 is lacking at the moment. See 6.0.4 for an example to check if that's the kind of thing you're after though |
Thanks @stevendarby, yep I went to the Releases page first. The first 4 releases at the top of the page didn't have any info, so I looked elsewhere. I think this team's release process needs a bit of polish to get that info up on there in a timely manner. |
The only issue fixed in 6.0.5 was Query exception after upgrading from 6.0.1 to 6.0.2 |
Hello
How can I find out what issues are fixed in a release?
e.g. yesterday I upgraded from 3.1.x to 6.0.4 and found an issue - I was getting an ArgumentException
Expression of type 'Task<List<ServiceAddOn>>' cannot be used for return type 'Task<IEnumerable<ServiceAddOn>>'
Today I upgraded to 6.0.5 and my issue was fixed, yay! I would like to see what issues were fixed in 6.0.5 so that I can find out the root cause.
Perhaps this project should Keep a Changelog?
The text was updated successfully, but these errors were encountered: