This is not the best solution, but it works!
We have several versions (changes could be only in the wrapper, but the cpp-module could not be changed)
- Version of cpp-module file (
pkg/src/python_onefile.cpp
) - Version of python wrapper on cpp-module file (
pkg/python/__init__.py
)
If cpp-module changes also should be changed module version, but if the wrapper is changed and cpp-module is not changed, then cpp-module version could be not changed.
- Change
release_notes.md
with changes. - Create a tag that starts with
v
, e.y.v0.0.1
orversion 0.0.1 release
orvery good
(also will trigger as it starts withv
). - Push
- Goto GitHub Actions page and choose workflow for your purpose: build and create a record on the release page.
- If you want to upload to the PyPI server, then add a user/password/token as documented in https://pypi.org/manage/account/token/.