Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.