release #14
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
on: | |
workflow_dispatch: | |
release: | |
types: | |
- published | |
name: release | |
jobs: | |
pypi: | |
name: upload release to PyPI | |
runs-on: ubuntu-latest | |
permissions: | |
id-token: write | |
steps: | |
- uses: actions/checkout@v3 | |
- uses: eifinger/setup-rye@v3 | |
- uses: actions/setup-python@v4 | |
with: | |
python-version: "3.12.2" | |
- name: build | |
run: rye build | |
- name: mint API token | |
id: mint-token | |
run: | | |
# retrieve the ambient OIDC token | |
resp=$(curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" \ | |
"$ACTIONS_ID_TOKEN_REQUEST_URL&audience=pypi") | |
oidc_token=$(jq -r '.value' <<< "${resp}") | |
# exchange the OIDC token for an API token | |
resp=$(curl -X POST https://pypi.org/_/oidc/mint-token -d "{\"token\": \"${oidc_token}\"}") | |
api_token=$(jq -r '.token' <<< "${resp}") | |
# mask the newly minted API token, so that we don't accidentally leak it | |
echo "::add-mask::${api_token}" | |
# see the next step in the workflow for an example of using this step output | |
echo "api-token=${api_token}" >> "${GITHUB_OUTPUT}" | |
- name: publish | |
# gh-action-pypi-publish uses TWINE_PASSWORD automatically | |
uses: pypa/gh-action-pypi-publish@release/v1 | |
with: | |
password: ${{ steps.mint-token.outputs.api-token }} |