-
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
chore(main): release 0.17.0 #234
chore(main): release 0.17.0 #234
Conversation
9d32ebe
to
f7ae00e
Compare
76e1118
to
d50d5f5
Compare
Let's make a new release to https://pypi.org/project/gyp-next because on Python 3.12 running
|
Was the pip package published manually? It seems @ryzokuken is the owner of the package. |
d50d5f5
to
812f0f0
Compare
418dbbf
to
36e20ac
Compare
@legendecas yes, I do remember manually pushing the package to PyPI at the time. I would really like to transfer ownership to the Node.js project at this point since I originally maintained gyp only to keep things going in the absence of a maintainer. |
How does package ownership work on PyPi? |
Maybe we should setup an org account for the project? |
I'm going to add @legendecas as maintainer just so there's no hard dependency on me and an action may be taken even when I'm unavailable... That said, as I was just discussing with @legendecas privately, the ideal situation would be to have a Node.js pypi account with properly managed credentials and setup GitHub actions to publish on release. |
36e20ac
to
950630d
Compare
950630d
to
e2ad6b1
Compare
Can we please get a release to PyPI? |
I'll publish new version today and setup publish automation as well. |
🤖 Release is at https://github.com/nodejs/gyp-next/releases/tag/v0.17.0 🌻 |
% |
🤖 I have created a release beep boop
0.17.0 (2024-04-29)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.