-
Notifications
You must be signed in to change notification settings - Fork 50
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
Breaking change from 8.1.2 to 8.2.0 #136
Comments
Yes, you are correct. Mistake. I'm not keen on reverting that PR. What do you think about putting out a new package as v9.0.0 and "unlist" 8.2.0? |
Sounds good |
Done. 8.2.0 has been marked as deprecated and points at 8.1.2 instead. And v9.0.0 has been released. Thanks for reporting. |
I do think we should consider releasing a minor version bump that reverts
it on the 8.* path. Having been on the receiving end of this kind of change
before, having a "latest" that fixes it helps if I consume a package that
consumed it but hasn't updated to latest or rolled back.
I guess concern is alleviated if we have a way to see on nuget if any
packages are saying >=8.2.0
…On Wed, Apr 29, 2020, 12:44 PM Daniel Wertheim ***@***.***> wrote:
Done. 8.2.0 has been marked as deprecated and points at 8.1.2 instead. And
v9.0.0 has been released. Thanks for reporting.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACSHCOUZQCWIUEFAOXZ7S6LRPB7SDANCNFSM4MO5A52A>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i got this error after upgrading from 8.1.2 to 8.2.0
this error was raised when trying to use version 8.2.0 with other nuget that was already compiled with version 8.1.2. to be more clear
Project A (with 8.2.0) ---> Nuget X ---> Ensure.That.8.1.2
The text was updated successfully, but these errors were encountered: