A) being overly restrictive, and declaring the current released version as your max, breaking for a short time on each new lang version
B) being psychic, and knowing when (without the aid of semver) your package might break
An unmaintained package will not be updated with the max flag when the breakage occurs.
Any package always declaring the current version will have to be updated for every new release.
Both seem like a lot of admin.
I know using unmaintained packages isn't ideal in the first place, but it happens, and packages exist that are pretty much "finished" and very light on bugs, if they were stable and heavily exercised for some time before losing their maintainers.
I.e. future compilers can understand previous version of the language spec.
This is different from python 3 because python 3 cannot run python 2 code, even if told that some library is python 2. That is where the migration pain came from.