You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for providing this library. We use it all the time.
I saw that you unlisted version 2.1.37 and that the latest stable release is in NuGet is 2.1.35 (). From the release notes 2.1.42 reverts a broken feature in 2.1.37 and 2.1.44 only updates the README, so in some sense 2.1.44 is functionally equivalent to 2.1.35. I guess it is up to you to define what is a release and what isn't.
However, releasing these versions in GitHub, but not on NuGet, seems to confuse our dependency version checker. This in turn confuses us.🙃 Would it be possible to either release these version on NuGet or label them as pre-releases similar to this https://github.com/microsoft/vstest/releases? It could be argued that the dependency checker should be based on NuGet, but this isn't the case at the moment.
The text was updated successfully, but these errors were encountered:
While doing my monthly .NET updates I stumpled upon this, too. In April I updated to 2.1.44, but now this packages is not found on NuGet.org. Should I revert to 2.1.35?
There are some changes relating to DateTime/TimeOnly that had to be reverted due to ... oddities; if you're not impacted, fine; either way, a new version will be deployed in due course
Hi!
Thanks for providing this library. We use it all the time.
I saw that you unlisted version 2.1.37 and that the latest stable release is in NuGet is 2.1.35 (). From the release notes 2.1.42 reverts a broken feature in 2.1.37 and 2.1.44 only updates the README, so in some sense 2.1.44 is functionally equivalent to 2.1.35. I guess it is up to you to define what is a release and what isn't.
However, releasing these versions in GitHub, but not on NuGet, seems to confuse our dependency version checker. This in turn confuses us.🙃 Would it be possible to either release these version on NuGet or label them as pre-releases similar to this https://github.com/microsoft/vstest/releases? It could be argued that the dependency checker should be based on NuGet, but this isn't the case at the moment.
The text was updated successfully, but these errors were encountered: