PyPI upload workflow uses trusted publisher instead of PyPI API token.

Signed-off-by: rafa-be <[email protected]>

.github/workflows/pypi.yml

@@ -9,29 +9,25 @@ permissions:
 
 jobs:
   deploy:
-
     runs-on: ubuntu-latest
-
+    environment: release
+    permissions:
+      id-token: write
     steps:
-      - uses: actions/checkout@v4
       - name: Checkout code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Set up Python 3.8
         uses: actions/setup-python@v5
         with:
           python-version: "3.8"
       - name: Install dependencies
         run: |
           python -m pip install --upgrade pip
-          pip install build twine
+          pip install build
           pip install -r requirements.txt
 
       - name: Build package
         run: python -m build
 
       - name: Publish to PyPI
-        env:
-          TWINE_USERNAME: __token__
-          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
-        run: |
-          python -m twine upload dist/*
+        uses: pypa/gh-action-pypi-publish@release/v1

README.md

@@ -13,6 +13,9 @@
     <a href="./LICENSE">
         <img src="https://img.shields.io/github/license/citi/parfun?label=license&colorA=0f1632&colorB=255be3">
     </a>
+    <a href="https://pypi.org/project/parfun/">
+      <img alt="PyPI - Version" src="https://img.shields.io/pypi/v/parfun?colorA=0f1632&colorB=255be3">
+    </a>
   </p>
 </div>
 

parfun/about.py

@@ -1 +1 @@
-__version__ = "7.0.1"
+__version__ = "7.0.2"