DOP-4242: Use release, not tag push for CI/CD

.github/workflows/README.md

@@ -2,6 +2,14 @@
 
 This README describes the various workflows defined for the docs-worker-pool repository.
 
+## Releases
+
+The release process occurs whenever someone releases a specific tag via the GitHub UI. Three separate workflows are run upon release:
+
+1. `deploy-prd-ecs.yml` - Builds and deploys the old Autobuilder to prd
+2. `deploy-prd-enhanced-webhooks.yml` - Builds and deploys webhooks (GitHub and Slack handlers) for the enhanced Autobuilder
+3. `deploy-prd-enhanced-worker.yml` - Builds and deploys the Autobuilder worker to prd
+
 ## Feature Branch Deploys
 
 The feature branch deploy process occurs whenever a developer opens a pull request. It consists of three separate workflows:

.github/workflows/deploy-prd-ecs.yml

@@ -1,7 +1,6 @@
 on:
-  push:
-    tags:
-      - 'v*'
+  release:
+    types: [released]
 concurrency:
   group: environment-prd-${{ github.ref }}
   cancel-in-progress: true

.github/workflows/deploy-prd-enhanced-webhooks.yml

@@ -1,8 +1,6 @@
 on:
-  push:
-    tags:
-      - 'v*'
-
+  release:
+    types: [released]
 concurrency:
   group: environment-prd-enhanced-webhooks-${{ github.ref }}
   cancel-in-progress: true

.github/workflows/deploy-prd-enhanced-worker.yml

@@ -1,8 +1,6 @@
 on:
-  push:
-    tags:
-      - 'v*'
-
+  release:
+    types: [released]
 concurrency:
   group: environment-prd-enhanced-worker-${{ github.ref }}
   cancel-in-progress: true

README.md

@@ -157,7 +157,8 @@ docs-worker-pool contains various triggers for release to higher environments. C
 
 - Create release tags. We currently follow [semver](https://semver.org/) standards.
 - If you don't have push access, open an issue or otherwise contact a contributor with administrator privileges.
-- Verify that the deploy-production-ec2 workflow executed successfully for both job runs across both production instances.
+- Create a release associated with the tag using the GitHub UI or by running `gh release create`. 
+- Verify that the deploy-production-ec2 workflow executed successfully for both job runs across both production instances. The workflow should only run when a release is published.
 
 ### Serverless Development