diff --git a/.github/workflows/plan-release.yml b/.github/workflows/plan-release.yml
index cd8b4352f..6cbde2968 100644
--- a/.github/workflows/plan-release.yml
+++ b/.github/workflows/plan-release.yml
@@ -57,7 +57,7 @@ jobs:
           node-version: 18
       - uses: pnpm/action-setup@v4
         with:
-          version: 9
+          version: 8.5
       - run: pnpm install --frozen-lockfile
       - name: "Generate Explanation and Prep Changelogs"
         id: explanation
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index 0ab91b117..832e403ba 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -51,7 +51,7 @@ jobs:
           registry-url: 'https://registry.npmjs.org'
       - uses: pnpm/action-setup@v4
         with:
-          version: 9
+          version: 8.5.0
       - run: pnpm install --frozen-lockfile
       - name: npm publish
         run: pnpm release-plan publish
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
deleted file mode 100644
index e7632ecdb..000000000
--- a/.github/workflows/release.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-name: Release
-
-on:
-  workflow_dispatch:
-    inputs:
-      tag:
-        required: true
-        type: string
-        description: 'Which tag do we want to retry? this should begin with v, and match exactly one of the tags present on the repo'
-  push:
-    tags:
-      - 'v*'
-
-jobs:
-  release:
-    name: 'Tagged Release'
-    runs-on: 'ubuntu-latest'
-
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.events.inputs.tag || github.ref }}
-      - uses: wyvox/action-setup-pnpm@v3
-        with:
-          node-registry-url: "https://registry.npmjs.org"
-      - run: pnpm build
-
-      # > This is not interactive right?
-      # correct
-      #
-      # > This doesn't bump the version, just publish right?
-      # correct
-      #
-      # > Do we have a way to tell it to ignore already published packages in case we need to re-run the job?
-      # this is default behavior
-      #
-      # > It will skip the private packages, presumably?
-      # yes
-      #
-      # > --force
-      #   Packages are proceeded to be published even if their current version is already in the
-      #   registry.
-      #
-      # > --no-git-checks
-      #   we publish from tags, and default behavior is to only allow publishing on main/master
-      - run: |
-          npm whoami --registry=https://registry.npmjs.org/
-          pnpm -r publish --access public --no-git-checks --force
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}