[User feedback] Creating versions compatible with new DHIS2 versions without changing package version

[EyeSeeTeaBotTest]

dhis2

Username: fernandezl

Browser

• Name: Mozilla
• Version: 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
• Platform: Win32

User report

URL: http://localhost:8080/api/apps/MetaData-Synchronization/index.html#/packages

Hello all!
When we upgrade the module to new DHIS2 versions but the module has not changed at all, I would like to give to the package the same version as previous packages. I want the version number to reflect true changes in the matata, indicators or module functionality and not just DHIS2 upgrades. However once I have created a package with a version, I can't use the same version to generate the same package in another DHIS2 version. I am currently changing the version manually in the file name after uploading to Git...but it is not ideal. Any ideas on how to address this use case?