Closed LiamPattinson closed 1 year ago
Done. Thanks @orso82 for a good build/release system.
@smithsp my standard workflow to release a new version is:
omas/omas/version
version X.Y.Z
and push (the format must be this for make tag
to work)make tag
make pypi
I suspect that you're skipping 1-3 in the process? or doing it somewhat differently?
I just forgot to git push
after step 2. In the Makefile
, it has git push --tags
, but that doesn't seem to pick up the branch push. I have now pushed it.
That explains it 👍
Though the commit message should have been version 0.91.0
. I am surprised that make tag
worked? Or maybe you tagged it manually?
I used make tag
. It seemed to work fine.
Thanks for this!
If there are issues with keeping things consistent with versioning, the approach I normally use is to have setuptools-scm create a _version.py
file dynamically from the git tags during installation, and the publishing step is handled by GitHub workflows (here's an example of how we do it in Pyrokinetics). That way, we only need to create a new release on GitHub, and both the in-package version file and the PyPI upload are handled automatically. I could try implementing something similar here if you're interested.
Thank you for the offer @LiamPattinson but at this point the process that we have works and it takes me just a few seconds to make a new release ;) also in OMAS a lot of things are done via the Makefile, so there is some consistency with that approach. But definitely something to keep in mind for new projects!
I'm finishing up some work on a PR for Pyrokinetics which is pulling in OMAS as a dependency, but since the latest updates to the build system aren't yet pushed to PyPI, I'm currently having to tell pip to install a specific git commit of OMAS rather than just using the version. Would it be possible to release a version 0.90.1/0.91?