fix: api tokens

ICIJ · Mar 14, 2024 · e5d679f · e5d679f
1 parent 64480dc
commit e5d679f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/.github/workflows/publish-common.yml b/.github/workflows/publish-common.yml
@@ -22,14 +22,14 @@ jobs:
       # We assume tests have run in a previous workflow and just build and publish
       - name: Build and publish
         env:
-          PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
+          PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN_ICIJ_COMMON }}
         # PyPi doesn't support orgs and user API token have to be put in here. Since tokens can be used either for a
         # single repo or all user repos, we have to use separate tokens for each asset to avoid providing access to
         # all user repos
         run: |
           cd icij-common
           poetry build
-          poetry config pypi-token.pypi ${{ env.PYPI_API_TOKEN_ICIJ_COMMON }}
+          poetry config pypi-token.pypi ${{ env.PYPI_API_TOKEN }}
           poetry publish
 
 concurrency:

diff --git a/.github/workflows/publish-worker.yml b/.github/workflows/publish-worker.yml
@@ -22,14 +22,14 @@ jobs:
       # We assume tests have run in a previous workflow and just build and publish
       - name: Build and publish
         env:
-          PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
+          PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN_ICIJ_WORKER }}
         # PyPi doesn't support orgs and user API token have to be put in here. Since tokens can be used either for a
         # single repo or all user repos, we have to use separate tokens for each asset to avoid providing access to
         # all user repos
         run: |
           cd icij-worker
           poetry build
-          poetry config pypi-token.pypi ${{ env.PYPI_API_TOKEN_ICIJ_WORKER }}
+          poetry config pypi-token.pypi ${{ env.PYPI_API_TOKEN }}
           poetry publish
 
 concurrency: