Nuget does not auto update stuff so it is safe to release a new package. However, when other packages have a dependancy to NHibernate 3 and they didn't set the correct dependancy version then they will automatically update to the latest version instead of updating to the latest non breaking.
http://docs.nuget.org/docs/reference/versioning So they should target like this: <dependency id="ExamplePackage" version="[3,4)" /> And not like: <dependency id="ExamplePackage" version="3" /> or not specify a version at all. -- Ramon On Mon, Mar 18, 2013 at 6:21 PM, Oskar Berggren <[email protected]>wrote: > Does anyone know... > > If we release NHibernate 4.x under the existing "NHibernate" Nuget > package name, containing binaries only for .Net 4.0, is the Nuget > client smart enough to suggest an update only for projects that > actually target .Net 4.0? Or will it try to update also projects that > target .Net 3.5? > > /Oskar > > -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
