Nuget package dependencies for 1.3.0 need some correction about mongorepository

[badcodelab]

In fact; I just did 😉

Wow! It is not actually needed but thanks!
Yes, I noticed that the >=2.0 driver is incompatible with MongoRepository yet but Nuget doesn't know this curious thing.
I didn't know that package owner cannot change dependencies after publishing new version.
Thanks a lot!

[RobThree]

A nuget package can't retroactively be changed (besides the title and some other meta-data that is). Is there a specific reason why you're on 1.3.0 anyway? Why not use any of the later versions (which, except 1.4.2 - 1.5.2, are fixed to specific mongocsharpdriver versions).

[badcodelab]

I use the latest package, but the case is following:
Each version requires strongly defined version of mongosharpdriver (e.g. latest one requires = 1.10.1 which is outdated) except MongoRepository 1.3.0 (it has >= 1.4.1 dependency).
And if you decide to update mongosharpdriver to 2.2.3 Nuget downgrades MongoRepository from 1.6.10 to 1.3.0

[RobThree]

The >=2.0 driver is incompatible with MongoRepository 1.x. There's a 2.0 version of MongoRepository in the works (feedback / help appreciated!).

The latest 1.x version of the mongocsharpdriver is 1.11 which is 1 version (and an RC) ahead of 1.10.1. Not that exciting (although I just noticed 1.11 supports MongoDB 3.2; however: I haven't noticed any problems with 1.10.1 on MongoDB 3.2 if memory serves me correctly). I could release a new 1.6.11* of MongoRepository with a dependency on 1.11. But that won't fix/change the behaviour you see now.

As said; you can't retroactively change NuGet packages so I'm not sure what you want me to do? Any suggestions?

* In fact; I just did 😉