Release automation (PyPI, changelog)

[simontaurus]

Set up release automation (PyPI publish, changelog generation).

Acceptance Criteria

• Automated PyPI publishing on tag/release
• Changelog generation from commits/PRs
• Release workflow documented

[raederan]

Decision with @simontaurus --> Changes to Automated PyPI publishing on tag/release -> new development of CI uses python semantic release, versioning will be automated via git commit messages (changlog will be provided via python semantic releases)

[raederan]

@simontaurus

Should Zenodo versions of oold-python include a leading “vX.Y.Z”?
Decision:

A) Consistency with the git repo version tag -> with a leading “v”
or
B) Consistency with PyPI (bare, PEP 440 / CFF style) -> without a leading “v”

Currently, the CFF file does not include a version (A); with future Python Semantic Releases, option B could be easily automated (using the same update mechanism as the pyproject.toml version bump).

recommendation: B ; this ensures to be conform with standards for regarding target publisher

[raederan]

Decision on B comes with PR #99 ;
addressing all remaining acceptance criteria ;

[simontaurus]

Go with B: bare version (PEP 440 / CFF style) for CITATION.cff / PyPI / Zenodo - conform with the target publishers. The leading v stays only in the git tag namespace.