Merge pull request #68 from mozilla-ai/sfriedowitz/trigger-test-on-wo…

…rkflow-dispatch

Update TestPyPI to only occur on manual workflow dispatch

.github/workflows/publish.yaml

@@ -1,8 +1,9 @@
 name: Publish to PyPI
 
 on: 
+  workflow_dispatch:
   release:
-    types: [created,released]
+    types: [released]
 
 jobs:
   publish:
@@ -24,7 +25,7 @@ jobs:
 
     - name: Publish to TestPyPI
       uses: pypa/[email protected]
-      if: github.event_name == 'release' && github.event.action == 'created'
+      if: github.event_name == 'workflow_dispatch'
       with:
         password: ${{ secrets.PYPI_TEST_KEY }}
         repository-url: https://test.pypi.org/legacy/

CONTRIBUTING.md

@@ -76,9 +76,9 @@ see the `examples/dev_submission` directory.
 
 `.github/workflows/publish.yaml` contains the GitHub Action used to publish wheels to PyPI.
 
-This workflow is triggered by the creation of GitHub Releases.
-Draft releases trigger publishing to TestPyPI,
-while full releases trigger the prod version.
+The publishing workflow can be triggered in two ways:
+1. Manually triggered on the GitHub Actions UI, which publishes the package to TestPyPI, or
+2. Triggered by the creation of a GitHub release, which publishes to real PyPI.
 
 When creating a GitHub release, make sure that the tag used for the release
 matches the version of the target code branch.

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "lm-buddy"
-version = "0.2.3-rc.1"
+version = "0.2.3"
 authors = [
     { name = "Sean Friedowitz", email = "[email protected]" },
     { name = "Aaron Gonzales", email = "[email protected]" },