Let me explain what the problem is.
Internally, mods check the version number when being parsed, since some mods contain multiple versions and the mod site has to check the version to serve you the right code.
My mods, for example, you'll mostly see in the package-info.xml file they use '2.0 RC1.2, 2.0 RC2' as the versions they support, plus sometimes 1.1 - 1.1.99.
One of the changes in 2.0 RC2 was a revision to how this was being done (which is why it's "broken") but in fact it isn't.
2.0 by definition means 2.0 final. Thus 2.0 is a "higher" version than 2.0 RC1.2 or 2.0 RC2 which is why it doesn't work.
In reality it isn't "broken". In my opinion, it's doing its job properly and mod authors will have to learn not to take such shortcuts.