-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate release publish to PyPI #29
Comments
|
@targos do you have |
I don't have any token. |
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... |
Is there anything we can do to help this along? PyPI is still stuck on 0.4 and #83 is now biting new installs. |
I can post the new release on PyPI manually but we need to figure out something long-term. |
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. |
Manually updated the package to |
I can work with you on it now that I learned from doing nodejs/tap2junit#49 |
Do we need a Node.js org on PyPI to handle this, or is there a better way? |
We could use this GH action: https://github.com/pypa/gh-action-pypi-publish
The text was updated successfully, but these errors were encountered: