Skip to content

Commit

Permalink
Setup Trusted Publisher deployment to PyPI (#25)
Browse files Browse the repository at this point in the history
Use this instead of the API tokens we used before. It's safer and easier
to use because it doesn't required generating tokens and pasting them to
GitHub.
  • Loading branch information
leouieda committed Mar 13, 2024
1 parent 13d0f2b commit 0632016
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions .github/workflows/pypi.yml
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,10 @@ jobs:
needs: build
# Only publish from the origin repository, not forks
if: github.repository_owner == 'fatiando' && github.event_name != 'pull_request'
environment: pypi
permissions:
# This permission allows trusted publishing to PyPI (without an API token)
id-token: write

steps:
- name: Checkout
Expand All @@ -109,8 +113,6 @@ jobs:
if: github.event_name == 'push'
uses: pypa/gh-action-pypi-publish@v1.8.14
with:
user: __token__
password: ${{ secrets.TEST_PYPI_TOKEN}}
repository_url: https://test.pypi.org/legacy/
# Allow existing releases on test PyPI without errors.
# NOT TO BE USED in PyPI!
Expand All @@ -120,6 +122,3 @@ jobs:
# Only publish to PyPI when a release triggers the build
if: github.event_name == 'release'
uses: pypa/gh-action-pypi-publish@v1.8.14
with:
user: __token__
password: ${{ secrets.PYPI_TOKEN}}

0 comments on commit 0632016

Please sign in to comment.