I appreciate Cosmos' intentions in this, but quite apart from the politeness of asking the author, there are more practical reasons for this being a bad idea.
It's simply this: If Cosmos releases a v4.8 of a library as an enhancement to v4.7, and then the original author suddenly reveals he has his own new version v4.8, then all of a sudden we have two v4.8 versions, which are different, by different people, and have different capabilities.
And then "hilarity" ensues. And by "hilarity" I mean a complete mess.
Do the update via a patch, not a replacement. Then if the author takes it upon himself to fix it, the patch can just be removed.... but having two different libraries - or even the possibility of two different libraries - with the same name and version number, but with different APIs... that's just asking for trouble.
