[WIP] PyPI publishing workflow continued

[andhus]

TODO:

• On tag: Make sure tag name matches version - or better infer version from tag, e.g. using versioneer
• Non-tagged builds should have a version with (something like) -dev-<SHORT_SHA> postfix
• Don't publish to TESTPyPI on every push (maybe only on special commit message or test-tag?)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3fe36c7) 100.00% compared to head (86d6813) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##            master       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            7         7           
  Lines          348       350    +2     
  Branches        79        79           
=========================================
+ Hits           348       350    +2     

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

[gaby]

This should be:

if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags') to avoid pushing during a PR

[andhus]

Well, that's not really a problem (?) I think this part is all good.

[gaby]

Enabling verbose will show what the issue is, but it seems the version format is not valid:

https://github.com/pypa/gh-action-pypi-publish?tab=readme-ov-file#for-debugging

[andhus]

Just didn't have time to finish this earlier @gaby . The invalid version is due to the latest valid tag is not picked up (the first one starting with v is not compatible with versioneer) and I'll just disable the TestPyPI publishing for now (there could be reasons to publish to test PyPI more frequently/on other triggers, but on every push is just silly :) this was the setup in the guide)