Versioning

[lionel42]

As discussed in #280 we will need to track versions correctly.

Best solution is to use github tags to create releases and versions automatically with CI.
I have done this in emiproc (https://github.com/C2SM-RCM/emiproc) and it works quite well.

[SutarPrasad]

Hi @lionel42 , you can also look at this for the uv setup used
https://github.com/openghg/openghg/blob/devel/.github/workflows/workflow.yaml

[lionel42]

@SutarPrasad I have added a tag v2.1.0 , but the job was still blocked. https://github.com/openghg/fluxie/tree/v2.1.0
Do you know why ? Do you have to do extra steps to publish in your other repos ?

[lionel42]

I tried debugging the job related to the tagging from : https://github.com/openghg/fluxie/actions/runs/23431452279/job/69137284007

I get this output, which makes me think there is an issue with the way the tag is not propagated somehow in the CI job.

2026-03-30T08:20:53.7140000Z Evaluating release_pypi.if
2026-03-30T08:20:53.7140000Z Evaluating: (success() && (((github.event_name == 'push') && startsWith(github.ref, 'refs/tags/') && !contains(github.ref_name, '-') && contains(github.ref_name, '.'))))
2026-03-30T08:20:53.7140000Z Expanded: (true && (('push' == 'push') && startsWith('refs/heads/devel', 'refs/tags/') && !contains(github.ref_name, '-') && contains(github.ref_name, '.')))
2026-03-30T08:20:53.7140000Z Result: false

@SutarPrasad Do you know if you take additional steps on openghg than just creating a new tag ?