I have some experience developing multi-version modules(https://github.com/GrigoriyMikhalkin/sqlboiler-paginate https://github.com/GrigoriyMikhalkin/sqlboiler-p

I have some experience developing multi-version modules(https://github.com/GrigoriyMikhalkin/sqlboiler-paginate https://github.com/GrigoriyMikhalkin/sqlboiler-paginate). And i quite disagree with this article. > new copy of the entire codebase What i have done in my module, and what i think is a common way -- is to move common codebase to common submodule, which will be used by all other versions. > Allow package maintainers to specify the major version simply by updating git tags Wouldn't it cause problems if developers would need to maintain multiple versions in parallel? > command has no way to automatically update to a new major version To be honest, i don't see why there should be auto update to new major versions, since, usually new major version means breaking changes to API.