If I'm not mistaken, this project using poetry, quite a few of those steps could be simplified using poetry build right. That's what I used for vpype at least.

Which steps specifically? Effectively all this does for the wheel and sdist is:

1. Checkout branch
2. Install the pip build tool
3. Build. This is done with pip because that is what pip would do when running pip install vsketch on the user end. The settings in pyproject.toml cause it download poetry and use it as the build backend. I don't think using poetry would necessarily save any steps.
4. Show a SHA256 signature of the files for verification
5. Upload the artifacts

It does the additional step of testing that the sdist is actually installable through pip after generating it on all three platforms. I then use a GitHub release action and the official Pypi action to upload to Pypi.

You can see an example tag build here: https://github.com/DaAwesomeP/vsketch/actions/runs/1243632046

just wanted to restart the discussion. Is there anything else that can be done?

Yes, I need to take the time to look into it. I might actually go for a slightly simpler setup similar to what I use for my vpype plug-ins.

That said, this discord conversation makes me question if it's actually a good idea to package/release vsketch.Vsketch and vsk together...