Closed FurqanHabibi closed 9 months ago
@ojii Let's try this? Perhaps we can create a new release while at it?
A couple more changes are coming soon so I want to wait for those
@FurqanHabibi just to check, after merging, to make a release the procedure is:
correct?
100% correct 👍
Make sure release tag == pyproject.toml version
- Change version in pyproject.toml
- Update docs/changelog.rst
- make a commit and push
- create a release on github
I recommend release-please
github action to automate all these steps.
It's pretty easy to set up and works pretty well.
(maybe expect one WAT moment, but still rather easy to figure out)
It does require following https://www.conventionalcommits.org/en/v1.0.0/ though.
Edit: CalVer support is still on TODO list: https://github.com/googleapis/release-please/issues/1848
Edit: CalVer support is still on TODO list: googleapis/release-please#1848
that's a no from me then.
https://github.com/python-semantic-release/python-semantic-release then?
I haven't tried it, but I think version_pattern
can be crafted smth like YY.patch
?
thanks, i'll do a release and try this thing then
As with AAPNS, this will automatically publish a new pypi release when a Github release is created.