edge cask publishes on pre-releases — spacedock@next skip_upload auto→false

The spacedock@next (edge) cask carried skip_upload: auto like stable, so a
hyphenated pre-release tag (release.prerelease: auto marks it pre-release) skipped
BOTH casks and the edge tap stayed stale. Set the edge cask's skip_upload to false
so it publishes on every tag including pre-releases. Stable stays auto so it never
publishes a pre-release.

Proven against goreleaser v2.16.0's real cask publish pipe (mock client): edge
false→publishes on v0.23.0-pre.2 and on a final; stable auto→skips on the -pre,
publishes on the final. goreleaser check passes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: clkao

.goreleaser.yaml

@@ -151,9 +151,11 @@ homebrew_casks:
   # devBranch=next binary that installs the `next` plugin. Its on-demand re-pull
   # cadence rides the unchanged next-publish.yml; goreleaser only emits the cask.
   - name: spacedock@next
-    # Same pre-release guard as the stable cask: a hyphenated (pre-release) tag
-    # skips the edge cask bump, while a final vX.Y.Z still publishes it.
-    skip_upload: auto
+    # `false` publishes the edge cask on every tag, including pre-releases, so the
+    # edge tap tracks `-pre` cuts. This diverges from the stable cask's `auto`
+    # (which skips on a pre-release) — the edge channel is meant to surface
+    # pre-release builds, while stable never gets a pre-release.
+    skip_upload: false
     ids:
       - spacedock-edge
     repository: