-
Notifications
You must be signed in to change notification settings - Fork 417
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
Publish to PyPi workflow broken #1483
Comments
Apologies if I am just stating the obvious, but there is this error in the log:
So it looks like there's something wrong with the PyPi user account? I believe the other warnings can be ignored for now. |
@Unrud has stepped back from this project, other maintainers are @gentooboontoo @liZe : can one of these please dig into? Related file: |
We could add a repository admin in the list of PyPI maintainers. Anyone interested? |
Add at least me, thank you very much, I have created now an account here: pbiering |
Done! |
@liZe : thank you for the invitation, but my current permissions on "Radicale" prevent me entering the "Settings" page and configure the required secret. According to https://github.com/marketplace/actions/pypi-publish an API token
must be configured, as it is a personal one it should be not disclosed here...so either you enrich my permissions or I send it to you by e-mail. |
@pbiering I’m not admin on GitHub. Maybe you can write a mail to @gentooboontoo 😄. |
@gentooboontoo : can you support here, a value must be set in Settings -> Security -> Secrets and variables -> Actions |
@gentooboontoo / @Unrud : any change to fix this? |
@gentooboontoo : thank you, received
and re-triggered the workflow, now 3.2.0 is visible here: https://pypi.org/project/Radicale/#history |
Sorry @pbiering, I missed the notification for the previous messages, hence the delay… |
This happened after the release of 3.2.0:
https://github.com/Kozea/Radicale/actions/runs/8943158465/job/24567264820
I have no experiences here, can one support me please? Looks like several things must be fixed...
The text was updated successfully, but these errors were encountered: