Skip to content
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

Rework PyPI dist release pipeline #198

Merged

Conversation

StykMartin
Copy link
Contributor

This pull request changes the way we publish artifacts to PyPI.
We no longer use secrets to publish artifacts, instead, artifacts are published to PyPI using a trusted publisher.
This approach is documented here - https://docs.pypi.org/trusted-publishers/.
The release pipeline is also part of the production environment. This means we can apply multiple rules and adjust the conditions for when the new release can be made (gating).

Also, we don't need multiple workflows to perform these actions, so I merged pipelines and used a strategy matrix to do the trick.

--
I plan to extend this definition to include production COPR builds in the next PR.

@StykMartin StykMartin requested review from p3ck and mdujava December 30, 2023 17:14
@StykMartin StykMartin force-pushed the wip/rework-release-pypi branch from db04064 to 1c163ee Compare December 30, 2023 17:16
@StykMartin StykMartin merged commit 8bb2169 into beaker-project:release-29 Dec 31, 2023
5 checks passed
@StykMartin StykMartin deleted the wip/rework-release-pypi branch December 31, 2023 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants