PKG: distribute single semver

[Borda]

What does this PR do?

unify all pkg versions
in case you run from source without install provide commit hash

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

cc @Borda @carmocca @akihironitta

[Borda]

ok, changed to have distributed the version.info so there is no overwrite of __version__.py 🦦
@carmocca @justusschock can you please check it again :)

[akihironitta]

Is there any assertion in CI to avoid distributing packages with the wrong version info? something like:

python -c "assert pl.__version__ == '${{ ... }}'"

[Borda]

Is there any assertion in CI to avoid distributing packages with the wrong version info? something like:

python -c "assert pl.__version__ == '${{ ... }}'"

good idea, we can also add in another PR, the if pypi release workflow is in action we would check if the generated version is the same as input git tag...