Add --force to pnpm publish to account for already published packages

glimmerjs · Oct 24, 2023 · a1b4ed4 · a1b4ed4
1 parent 2b6952e
commit a1b4ed4
Showing 1 changed file with 8 additions and 1 deletion.
diff --git 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 }}