ci(publish): drop fetch-tags on self-hosted checkout

actions/checkout@v4 on self-hosted lux-build conflicts when both the
target commit and the tag ref are passed to the same fetch refspec.
Letting checkout resolve the tag implicitly (via the trigger ref)
avoids the "Cannot fetch both <sha> and refs/tags/v1.1.x" error.

.github/workflows/publish.yml

@@ -30,7 +30,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
         with:
-          fetch-tags: true
+          # On tag push the checkout action already resolves the tag ref;
+          # setting fetch-tags here on a self-hosted runner conflicts with
+          # the refspec the runner uses, so we leave it implicit.
+          fetch-depth: 1
 
       - uses: actions/setup-node@v4
         with:

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bridge",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "Lux Bridge - Decentralized cross-chain bridge using MPC",
   "packageManager": "[email protected]",
   "main": "index.js",