OIDC-based releases #904
Merged
OIDC-based releases #904
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JBWilkie
force-pushed
the
PLA-1049-OIDC-releases
branch
6 times, most recently
from
a112080 to
6425751
Compare
JBWilkie
force-pushed
the
PLA-1049-OIDC-releases
branch
from
6425751 to
ec1a524
Compare
RileyWilliams
approved these changes
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
Currently, we use static user credentials for PyPi to release new darwin-py versions. Ideally, static credentials should not be used
Solution
This PR adjusts the release process to authenticate with PyPi via OIDC, which uses short-lived tokens. This guide was followed: https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-pypi
Changelog
Removed the need for static credentials when publishing versions of darwin-py