I appreciate the work you put in this, but we're already using release-please to create the release, so I'm surprised you're not adding something to the existing workflow.

release-please doesn't publish the package to the registry. I'll merge the two workflow so that they can be pipelined. Thanks for the suggestion!

This is ready for review. I ran it on my own repo and published https://test.pypi.org/project/gyp-next/0.18.0.post1/

It is a shame that GitHub Packages still lacks support for the Python Packaging Index (PyPI). https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#support-for-package-registries

Well, yeah, no idea why pypi api isn't supported.

@legendecas legendecas#2

@cclauss @targos would you mind taking a look again? thank you!

I'd prefer someone else to review as I did part of the changes and I'm not familiar with the release of Python packages.