Use dynamic versioning

[CM000n]

In my opinion, it means additional, actually unnecessary effort and causes potential errors that the package version number in pyproject.toml has to be adjusted each time to a version number matching the publishing tag. Also a separate MR has to be created every time for just bumping the version number in such manner.

My suggestion would therefore be to use dynamic versioning: https://github.com/mtkennerly/poetry-dynamic-versioning
This uses the version number specified in the repository tag to build the python package each time during the poetry build process.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (70526ac) 72.47% compared to head (4a3cc65) 72.47%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #274   +/-   ##
=======================================
  Coverage   72.47%   72.47%           
=======================================
  Files          28       28           
  Lines        1355     1355           
=======================================
  Hits          982      982           
  Misses        373      373           

Flag	Coverage Δ
unittests	72.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[DurgNomis-drol]

Love this! Always thought to think about away to do this.