Skip to content
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

Should Version 2.16 Have Been a Major Version? #338

Open
Vaccano opened this issue Mar 10, 2020 · 0 comments
Open

Should Version 2.16 Have Been a Major Version? #338

Vaccano opened this issue Mar 10, 2020 · 0 comments

Comments

@Vaccano
Copy link

Vaccano commented Mar 10, 2020

The fix to issue #279 causes a conflict when an application uses 2 NuGets that use this library when:

  1. One of the NuGets depends on a pre-change version (2.15.4 for me)
  2. Another that depends on a post change version (2.17 for me)

Basically, the pre-change dependency is looking for a jil.core assembly and cannot find it in the newer version. (See this stack overflow question for details: https://stackoverflow.com/questions/60609571/nuget-package-is-looking-for-exact-version).

I am wondering if that fix (published in 2.16) should have been a major version change? My problem is that the first nuget is automatically upgrading to the later minor versions assuming them to be backwards compatible.

Probably too late to fix now. But I thought I would note that it is causing issues (at least for me).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant