gyp-next Automate release publish to PyPI

We could use this GH action: https://github.com/pypa/gh-action-pypi-publish

Apr 03 '20 12:04 targos

~https://github.com/nodejs/gyp-next/packages is an alternative approach.~ Python not supported.

Apr 03 '20 12:04 cclauss

@targos do you have PYPI_API_TOKEN or @ryzokuken has ? This need to configured to settings if I understand correctly.

Aug 26 '22 15:08 gengjiawen

I don't have any token.

Aug 29 '22 08:08 targos

I suppose you'd need a token from my account? Or could I add a new "Node.js" user to the package and we could use the token for that...

Aug 29 '22 15:08 ryzokuken

Is there anything we can do to help this along? PyPI is still stuck on 0.4 and https://github.com/nodejs/gyp-next/pull/83 is now biting new installs.

Mar 02 '23 12:03 dennisjackson

I can post the new release on PyPI manually but we need to figure out something long-term.

Mar 03 '23 11:03 ryzokuken

Agreed with @dennisjackson I've just run into this for the first time trying to build an unrelated piece of software which is using gyp-next somewhere in its build system... and my build machine has Python 3.11.

Mar 10 '23 21:03 kpfleming

Manually updated the package to 0.15.0 on PyPI (https://pypi.org/project/gyp-next/0.15.0/) since it was very outdated and didn't work with Python 3.11 which is what most distros will soon switch to. Please feel free to contact me if you want to set up an automated pipeline for this.

Apr 19 '23 10:04 ryzokuken

I can work with you on it now that I learned from doing nodejs/tap2junit#49

Apr 19 '23 10:04 cclauss

Do we need a Node.js org on PyPI to handle this, or is there a better way?

Apr 19 '23 11:04 ryzokuken