The minor version has been incremented twice since I screwed up twice. PyPi does not allow you to re-use or write over the top of previous versions, sensibly, so I had to increment it. The README.md for this repo will have be modified to better suit what PyPi expects, it would be neater for us too.
Once merged, the steps noted in Manually Publishing will be complete for you, and the version will be incremented based on your second commit message key value type:
The minor version has been incremented twice since I screwed up twice. PyPi does not allow you to re-use or write over the top of previous versions, sensibly, so I had to increment it. The
README.md
for this repo will have be modified to better suit what PyPi expects, it would be neater for us too.Manually Publishing
flit
python3 -m pip install flit
__version__
injupyter_micropython_kernel/__init__.py
flit publish
Thoughts on automated publishing
Ideally, it would be best if there was a way to automate these steps using github actions.
Once automated, the workflow would be:
git checkout -b feature-name
git commit -m "added bla" -m "type: minor"
(major | minor)master
Manually Publishing
will be complete for you, and the version will be incremented based on your second commit message key valuetype: