-
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 PYPI_TOKEN
#150
Comments
In #147, the PyPi publishing issue was introduced by this action: In the
So, that's why we added a On PyPi, connected as openfisca-bot, we can see that there is 1 token by repository. For now, PyPi allows either 1 token for all repositories or 1 for each repository (aka PyPi project). As we have multiple teams and countries in openfisca, the decision was made to give 1 token per PyPi project. If you agree with this solution, I think that we need to remove the |
Thanks for these clarifications! Issuing one token per repo sounds like a much safer option, it's great 🙂 @sandcha if you have the rights to issue such a token, could you set one up and store it as |
We have a
PYPI_TOKEN
secret defined at organisation level in GitHub Actions. It however does apparently not grant access for publishing packages on PyPI, as we discovered in #147.If this value is simply improper, we should replace its content with a new token that enables PyPI publishing, so we can publish the latest version of the Country Template and check that CD works properly.
If it is right and has another use, a new token should be issued and stored with that same name in this repository secrets so that it shadows it.
In either case, after change, we should re-run the last Deploy workflow, so that we can check that the latest CD changes are operational.
The text was updated successfully, but these errors were encountered: