that's just how the versioning scheme works for easyconfigs

the idea is that, at some point, we can/will release only new easyconfigs (or updates to them) for software we already support, which require no changes to framework/easyblocks at all

That's *very* long term though, but I think it makes sense.