Hi Brant Burnett
We aren't upgrading for the sake of it, we're in a bit of a complicated state because of the way Common.Logging do their packaging. The current solution dependencies are:
Common.Logging - 3.3.1
Common.Logging.Log4Net1213 - 3.3.1
Log4Net - 2.0.7
The problem here, and we're not sure how we got into this situation, is that Log4Net1213 actually has a pinned dependency on Log4Net 2.0.3. This prevents the nuget cli from upgrading either Common.Logging or Common.Logging.Log4Net. A further complication is that the Common.Logging.Log4Net207 package (one that has the Log4Net 2.0.7 dependency) only has two available versions, 3.4.0 and 3.4.1.
My proposed changes are:
replace Common.Logging.Log4Net1213 (Log4Net 2.0.3) with Common.Logging.Log4Net207 (Log4Net 2.0.7)
upgrade Common.Logging and Common.Logging.Core to 3.4.1
An alternative would be to downgrade Log4Net from 2.0.7 to 2.0.3, which would allow the Common.Logging.* packages to remain at 3.3.1 but allow consumer upgrade if desired.
It's not an easy decision, but don't want to leave it in a known "bad" state where consumers can't upgrade packages or make a changes.