fix(ci): publish Python distributions as

  release assets

Author: alexandreteles

.github/workflows/release.yml

@@ -121,8 +121,7 @@ jobs:
     needs: release
     runs-on: ubuntu-latest
     permissions:
-      contents: read
-      packages: write
+      contents: write
     steps:
       - uses: actions/checkout@v4
         with:
@@ -136,13 +135,15 @@ jobs:
         run: uv sync --python 3.14
       - name: Build package
         run: uv build
-      - name: Install Twine
-        run: python -m pip install --upgrade twine
-      - name: Publish package
+      - name: Upload workflow artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-${{ needs.release.outputs.tag }}
+          path: dist/*
+      - name: Upload release assets
         env:
-          TWINE_PASSWORD: ${{ secrets.GITHUB_TOKEN }}
-          TWINE_USERNAME: ${{ github.actor }}
-        run: python -m twine upload --repository-url https://api.github.com/orgs/${{ github.repository_owner }}/packages/pypi/upload dist/*
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: gh release upload "${{ needs.release.outputs.tag }}" dist/* --clobber
 
   build-release-docs:
     if: needs.release.outputs.released == 'true'

README.md

@@ -33,8 +33,9 @@ pip install fastapi-paseto
 ```
 
 Releases are built from GitHub Actions after a successful semantic release on
-`master`. If you consume the package from the repository's GitHub Packages
-index, configure your Python package index credentials before installing.
+`master`. Each release publishes the wheel and source distribution as GitHub
+workflow artifacts and as downloadable assets on the corresponding GitHub
+Release.
 
 `AuthPASETO.load_config()` now expects a callback that returns either a plain
 mapping or a `pydantic-settings` `BaseSettings` instance. A minimal setup looks
@@ -63,7 +64,8 @@ headers`.
 
 The release workflow runs tests, builds the package, builds the docs, creates
 the next semantic version, updates the generated changelog, publishes the
-distribution to GitHub Packages, and deploys the latest docs to GitHub Pages.
+distribution as GitHub Release assets and workflow artifacts, and deploys the
+latest docs to GitHub Pages.
 The first automated release should start from a bootstrap tag that matches the
 current project version.