Closed moorec-aws closed 3 months ago
PyPI publishing does not support reusable workflows, there is an open issue to add support:
https://github.com/pypi/warehouse/issues/11096
For now we need to keep publishing to pypi as a job in the publish workflow file of each repository so that it can authenticate to publish.
The Release job in the reusable publish workflow requires contents write permissons.
https://github.com/OpenJobDescription/.github/blob/mainline/.github/workflows/reusable_publish.yml#L35
Move PyPI publishing job back to each repository instead of using a reusable workflow
Tested in a developer github account
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issues 0 New issues 0 Accepted issues
Measures 0 Security Hotspots No data about Coverage 0.0% Duplication on New Code
See analysis details on SonarCloud
What was the problem/requirement? (What/Why)
PyPI publishing does not support reusable workflows, there is an open issue to add support:
https://github.com/pypi/warehouse/issues/11096
For now we need to keep publishing to pypi as a job in the publish workflow file of each repository so that it can authenticate to publish.
The Release job in the reusable publish workflow requires contents write permissons.
https://github.com/OpenJobDescription/.github/blob/mainline/.github/workflows/reusable_publish.yml#L35
What was the solution? (How)
What is the impact of this change?
Move PyPI publishing job back to each repository instead of using a reusable workflow
How was this change tested?
Tested in a developer github account
Was this change documented?
no
Is this a breaking change?
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.