From a1b4ed4d278b1b1cc085705895e7430897850f8f Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Mon, 23 Oct 2023 22:08:49 -0400
Subject: [PATCH] Add --force to pnpm publish to account for already published
 packages

---
 .github/workflows/release.yml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 01baa462f..e7632ecdb 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -36,8 +36,15 @@ jobs:
       #
       # > 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
+          pnpm -r publish --access public --no-git-checks --force
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}