From 537bc1b6dbd527fac7ef52e9b1c7290d8036b64a Mon Sep 17 00:00:00 2001
From: Diego Hurtado <ocelotl@users.noreply.github.com>
Date: Wed, 28 Aug 2024 15:32:34 -0600
Subject: [PATCH] Skip testpypi

---
 .github/workflows/release.yml | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index b45ff25e719..dfe0f9f443c 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -75,19 +75,6 @@ jobs:
         run: |
           pip install twine
 
-      # The step below publishes to testpypi in order to catch any issues
-      # with the package configuration that would cause a failure to upload
-      # to pypi. One example of such a failure is if a classifier is
-      # rejected by pypi (e.g "3 - Beta"). This would cause a failure during the
-      # middle of the package upload causing the action to fail, and certain packages
-      # might have already been updated, this would be bad.
-      - name: Publish to TestPyPI
-        env:
-          TWINE_USERNAME: '__token__'
-          TWINE_PASSWORD: ${{ secrets.test_pypi_token }}
-        run: |
-          twine upload --repository testpypi --skip-existing --verbose dist/*
-
       - name: Publish to PyPI
         env:
           TWINE_USERNAME: '__token__'