CI: trigger wheels workflow on GitHub release (add release:published)

Author: evgenii

.github/workflows/wheels.yml

@@ -13,6 +13,8 @@
 name: Wheel builder
 
 on:
+  release:
+    types: [published]
   schedule:
   # 3:27 UTC every day
   - cron: "27 3 * * *"
@@ -222,7 +224,7 @@ jobs:
 
   publish:
     if: >
-      github.repository == 'evgmosme/pandas' &&
+      github.repository == 'pandas-dev/pandas' &&
       github.event_name == 'push' &&
       startsWith(github.ref, 'refs/tags/v')
 
@@ -233,7 +235,7 @@ jobs:
     runs-on: ubuntu-latest
 
     environment:
-      name: testpypi          # must match the Environment in repo settings
+      name: pypi
     permissions:
       id-token: write         # OIDC for Trusted Publishing
       contents: read
@@ -252,22 +254,9 @@ jobs:
                     -name '*.whl'   -exec mv {} upload/ \;
           find dist -name '*.tar.gz' -exec mv {} upload/ \;
 
-      - name: Publish to **Test PyPI** (Trusted Publishing)
+      - name: Publish to **PyPI** (Trusted Publishing)
         uses: pypa/gh-action-pypi-publish@release/v1
         with:
-          repository-url: https://test.pypi.org/legacy/
+          repository-url: https://upload.pypi.org/legacy/
           packages-dir: upload
           skip-existing: true
-
-    # environment:
-    #   name: pypi
-    # permissions:
-    #   id-token: write
-    #   contents: read
-    #
-    # - name: Publish to **PyPI** (Trusted Publishing)
-    #   uses: pypa/gh-action-pypi-publish@release/v1
-    #   with:
-    #     repository-url: https://upload.pypi.org/legacy/
-    #     packages-dir: upload
-    #     skip-existing: true

doc/source/development/maintaining.rst

@@ -445,9 +445,9 @@ which will be triggered when the tag is pushed.
    - Set as the latest release: Leave checked, unless releasing a patch release for an older version
      (e.g. releasing 1.4.5 after 1.5 has been released)
 
-5. Upload wheels to PyPI::
-
-    twine upload pandas/dist/pandas-<version>*.{whl,tar.gz} --skip-existing
+5. Wheels are uploaded automatically by GitHub Actions
+   via **Trusted Publishing** when the GitHub *Release*
+   is published. No manual ``twine upload`` step is required.
 
 6. The GitHub release will after some hours trigger an
    `automated conda-forge PR <https://github.com/conda-forge/pandas-feedstock/pulls>`_.