Update the release process (#102)

* remove the syncing step for stable

* use build instead of the deprecated pep517.build [skip-ci]

* only upload to pypi on the main repository [skip-ci]

Author: keewis

.github/workflows/pypi.yaml

@@ -7,6 +7,7 @@ on:
 jobs:
   deploy:
     runs-on: ubuntu-latest
+    if: github.repository == 'xarray-contrib/pint-xarray'
     steps:
       - uses: actions/checkout@v1
       - name: Set up Python
@@ -15,10 +16,11 @@ jobs:
           python-version: '3.x'
       - name: Install dependencies
         run: |
-          python -m pip install --upgrade pip pep517 twine
+          python -m pip install --upgrade pip
+          python -m pip install build twine
       - name: Build
         run: |
-          python -m pep517.build --source --binary --out-dir dist/ .
+          python -m build --sdist --wheel --outdir dist/ .
       - name: Check the built archives
         run: |
           twine check dist/*

HOW_TO_RELEASE.rst

@@ -31,14 +31,6 @@ Release process
 8. Draft a release for the new tag on github. A CI will pick that up, build the project
    and push to PyPI. Be careful, this can't be undone.
 
-9. Update stable:
+9. Make sure readthedocs builds both `stable` and the new tag
 
-    .. code:: sh
-
-       git checkout stable
-       git merge v0.X.Y
-       git push origin stable
-
-10. Make sure readthedocs builds both `stable` and the new tag
-
-11. Add a new section to `whats-new.rst` and push directly to master
+10. Add a new section to `whats-new.rst` and push directly to master