Merge branch 'release-workflow' of https://github.com/lzchen/opentelemetry-python

Author: lzchen

.github/workflows/publish.yml

@@ -96,6 +96,37 @@ jobs:
                             --discussion-category announcements \
                             v$STABLE_VERSION
 
+      - uses: actions/setup-python@v1
+        with:
+          python-version: '3.7'
+
+      - name: Build wheels
+        run: ./scripts/build.sh
+
+      - name: Install twine
+        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__'
+          TWINE_PASSWORD: ${{ secrets.pypi_password }}
+        run: |
+          twine upload --skip-existing --verbose dist/*
+
       - uses: actions/checkout@v3
         with:
           # the step below is creating a pull request against main

.github/workflows/release.yml

@@ -2,22 +2,22 @@
 
 ## Preparing a new major or minor release
 
-* Run the [Prepare release branch workflow](https://github.com/trask/repository-template/actions/workflows/prepare-release-branch.yml).
+* Run the [Prepare release branch workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/prepare-release-branch.yml).
   * Press the "Run workflow" button, and leave the default branch `main` selected.
   * Review and merge the two pull requests that it creates
     (one is targeted to the release branch and one is targeted to `main`).
 
 ## Preparing a new patch release
 
 * Backport pull request(s) to the release branch.
-  * Run the [Backport workflow](https://github.com/trask/repository-template/actions/workflows/backport.yml).
+  * Run the [Backport workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/backport.yml).
   * Press the "Run workflow" button, then select the release branch from the dropdown list,
     e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
     then click the "Run workflow" button below that.
   * Review and merge the backport pull request that it generates.
 * Merge a pull request to the release branch updating the `CHANGELOG.md`.
   * The heading for the unreleased entries should be `## Unreleased`.
-* Run the [Prepare patch release workflow](https://github.com/trask/repository-template/actions/workflows/prepare-patch-release.yml).
+* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/prepare-patch-release.yml).
   * Press the "Run workflow" button, then select the release branch from the dropdown list,
     e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
   * Review and merge the pull request that it creates for updating the version.