Update release docs for new publish workflow, remove old publish step

ksunden · ksunden · commit 9071543f4f7a · 2025-12-11T15:11:55.000-06:00
diff --git a/.github/workflows/cibuildwheel.yml b/.github/workflows/cibuildwheel.yml
@@ -192,32 +192,3 @@ jobs:
           name: cibw-wheels-${{ runner.os }}-${{ matrix.cibw_archs }}
           path: ./wheelhouse/*.whl
           if-no-files-found: error
-
-  publish:
-    if: github.repository == 'matplotlib/matplotlib' && github.event_name == 'push' && github.ref_type == 'tag'
-    name: Upload release to PyPI
-    needs: [build_sdist, build_wheels]
-    runs-on: ubuntu-latest
-    environment: release
-    permissions:
-      id-token: write
-      attestations: write
-      contents: read
-    steps:
-      - name: Download packages
-        uses: actions/download-artifact@018cc2cf5baa6db3ef3c5f8a56943fffe632ef53  # v6.0.0
-        with:
-          pattern: cibw-*
-          path: dist
-          merge-multiple: true
-
-      - name: Print out packages
-        run: ls dist
-
-      - name: Generate artifact attestation for sdist and wheel
-        uses: actions/attest-build-provenance@977bb373ede98d70efdf65b84cb5f73e068dcc2a  # v3.0.0
-        with:
-          subject-path: dist/matplotlib-*
-
-      - name: Publish package distributions to PyPI
-        uses: pypa/gh-action-pypi-publish@ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e  # v1.13.0
diff --git a/doc/devel/release_guide.rst b/doc/devel/release_guide.rst
@@ -383,12 +383,23 @@ Building binaries
 =================
 
 We distribute macOS, Windows, and many Linux wheels as well as a source tarball via
-PyPI. Most builders should trigger automatically once the tag is pushed to GitHub:
+PyPI.
 
 * Windows, macOS and manylinux wheels are built on GitHub Actions. Builds are triggered
-  by the GitHub Action defined in :file:`.github/workflows/cibuildwheel.yml`, and wheels
+  by the GitHub Action defined in a separate
+  `release repository <https://github.com/matplotlib/matplotlib-release>`__, and wheels
   will be available as artifacts of the build. Both a source tarball and the wheels will
   be automatically uploaded to PyPI once all of them have been built.
+* To trigger the build for the ``matplotlib-release`` repository:
+
+  * If not already created, create a release branch for the meso version (e.g. ``v3.10.x``)
+  * Edit the ``SOURCE_REF_TO_BUILD`` environment variable at the top of
+    `wheels.yml <https://github.com/matplotlib/matplotlib-release/blob/main/.github/workflows/wheels.yml>`__
+    on the release branch to point to the release tag.
+  * Run the workflow from the release branch, with "pypi" selected for the pypi environment
+    using the `Workflow Dispatch trigger <https://github.com/matplotlib/matplotlib-release/actions/workflows/wheels.yml>`__
+  * This will run cibuildwheel and upload to PyPI using the Trusted Publishers GitHub Action.
+
 * The auto-tick bot should open a pull request into the `conda-forge feedstock
   <https://github.com/conda-forge/matplotlib-feedstock>`__. Review and merge (if you
   have the power to).
