EntityFrameworkCore.Exceptions.SqlServer 6.0.3.2 increases the dependency on Microsoft.Data.SqlClient from 4.1.0 to 5.1.1.
According to semantic versioning, this would mean that EntityFrameworkCore.Exceptions.SqlServer has to also be a major release. And exactly that just broke our software.
One part of the software updated from 6.0.3.1 to 6.0.3.2 while another module (pre-compiled) was still on 6.0.3.1, getting the newer SqlClient as transitive dependency and having the Encrypt property of the SqlConnectionStringBuilder fail only at runtime. Since there are no upper limits defined in the dependencies, no warning will be issued on creating the top-level project referencing those.
Please try to follow semantic versioning guidelines to avoid issues for other developers. I would advise to re-release as 7.0.0 and de-list the version from NuGet to not break others as well.
EntityFrameworkCore.Exceptions.SqlServer
6.0.3.2 increases the dependency onMicrosoft.Data.SqlClient
from 4.1.0 to 5.1.1.According to semantic versioning, this would mean that
EntityFrameworkCore.Exceptions.SqlServer
has to also be a major release. And exactly that just broke our software.One part of the software updated from 6.0.3.1 to 6.0.3.2 while another module (pre-compiled) was still on 6.0.3.1, getting the newer SqlClient as transitive dependency and having the
Encrypt
property of theSqlConnectionStringBuilder
fail only at runtime. Since there are no upper limits defined in the dependencies, no warning will be issued on creating the top-level project referencing those.Please try to follow semantic versioning guidelines to avoid issues for other developers. I would advise to re-release as 7.0.0 and de-list the version from NuGet to not break others as well.