@@ -107,25 +107,25 @@ jobs:
107
107
run : |
108
108
pip install twine
109
109
110
- # The step below publishes to testpypi in order to catch any issues
111
- # with the package configuration that would cause a failure to upload
112
- # to pypi. One example of such a failure is if a classifier is
113
- # rejected by pypi (e.g "3 - Beta"). This would cause a failure during the
114
- # middle of the package upload causing the action to fail, and certain packages
115
- # might have already been updated, this would be bad.
116
- - name : Publish to TestPyPI
117
- env :
118
- TWINE_USERNAME : ' __token__'
119
- TWINE_PASSWORD : ${{ secrets.test_pypi_token }}
120
- run : |
121
- twine upload --repository testpypi --skip-existing --verbose dist/*
122
-
123
- - name : Publish to PyPI
124
- env :
125
- TWINE_USERNAME : ' __token__'
126
- TWINE_PASSWORD : ${{ secrets.pypi_password }}
127
- run : |
128
- twine upload --skip-existing --verbose dist/*
110
+ # # The step below publishes to testpypi in order to catch any issues
111
+ # # with the package configuration that would cause a failure to upload
112
+ # # to pypi. One example of such a failure is if a classifier is
113
+ # # rejected by pypi (e.g "3 - Beta"). This would cause a failure during the
114
+ # # middle of the package upload causing the action to fail, and certain packages
115
+ # # might have already been updated, this would be bad.
116
+ # - name: Publish to TestPyPI
117
+ # env:
118
+ # TWINE_USERNAME: '__token__'
119
+ # TWINE_PASSWORD: ${{ secrets.test_pypi_token }}
120
+ # run: |
121
+ # twine upload --repository testpypi --skip-existing --verbose dist/*
122
+
123
+ # - name: Publish to PyPI
124
+ # env:
125
+ # TWINE_USERNAME: '__token__'
126
+ # TWINE_PASSWORD: ${{ secrets.pypi_password }}
127
+ # run: |
128
+ # twine upload --skip-existing --verbose dist/*
129
129
130
130
- uses : actions/checkout@v3
131
131
with :
0 commit comments