-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update on PyPI #24
Comments
I just found this issue. I started working on automating the updating in #26 However, as far as I am aware there are some issues regarding the ownership that needs to be resolved first. |
Alright, so since the access to the account managing the package on pypi got lost, I discusses with @mayhem if its feasible to rename the package. I think the least controversial suggestion have been Renaming has some obvious disadvantages:
This is what comes to my mind. I don't know who the responsible parties are, just let me know what you think! |
@mayhem We could do a pre-release to test the pipeline and do a proper release afterwards so everyone can update the dependency. What do you think? |
@phw Just a notice for you as author, |
Just started with the pre-release --- lets see how it goes. |
It failed -- are you able to see the results? How do we add the needed tokens? |
@mayhem in pypi.org go to https://pypi.org/manage/project/liblistenbrainz/settings/publishing/ and add a new trusted publisher. Repository: metabrainz/liblistenbrainz Not sure what would happen if the project does not yet exist on pypi, though. Might be this would need a manual publishing the very first time. |
@mayhem Should work without project also, on https://pypi.org/manage/account/publishing/ . Just use "liblistenbrainz" as project name there. |
Just for completeness, the project would be created then. No manual intervention required |
Update this package on https://pypi.org/project/pylistenbrainz/
The text was updated successfully, but these errors were encountered: