release: don't let a WinGet publish failure block Scoop/Homebrew

Publish to WinGet ran before Update Homebrew tap, and GitHub Actions
stops a job at its first failed step by default — so any WinGet
failure was silently skipping the Homebrew tap update too, even
though the two publish targets are unrelated. This was masked on the
v0.10.0 release only because Scoop happens to run earlier in the file
and had already pushed before WinGet failed.

vedantmgoyal9/winget-releaser also can't submit a package that has
never been published to winget-pkgs before — it only updates an
existing manifest — so until casablanque-code.zt is submitted once
manually (wingetcreate submit), this step is expected to fail on
every release.

Add continue-on-error to the WinGet step so Homebrew still runs
after it regardless, then a final always()-gated step that checks
steps.winget.outcome and fails the job (with a pointer to the
wingetcreate fix) if WinGet didn't succeed — so the gap stays visible
without blocking the other two targets.

Author: casablanque-code

.github/workflows/release.yml

@@ -93,6 +93,18 @@ jobs:
           fi
           
       - name: Publish to WinGet
+        id: winget
+        # continue-on-error: a WinGet publish failure shouldn't block the
+        # Homebrew tap update below it — they're independent publish
+        # targets. winget-releaser also cannot submit an *unpublished*
+        # package (only update an existing manifest in winget-pkgs), so
+        # until casablanque-code.zt has been manually submitted once via
+        # `wingetcreate submit` this step is *expected* to fail on every
+        # release — continue-on-error lets the rest of the release
+        # proceed in the meantime, and the final "Check publish results"
+        # step below still fails the job overall so the gap doesn't go
+        # unnoticed once winget-pkgs does have the package.
+        continue-on-error: true
         uses: vedantmgoyal9/winget-releaser@v2
         with:
           identifier: casablanque-code.zt # pkg name at microsoft/winget-pkgs
@@ -158,3 +170,15 @@ jobs:
             git commit -m "chore(homebrew): bump formula to ${GITHUB_REF_NAME}"
             git push origin main
           fi
+
+      - name: Check publish results
+        # Runs after every other publish step regardless of the WinGet
+        # outcome (that's the point of continue-on-error above), then
+        # surfaces the WinGet failure here so it isn't silently
+        # swallowed — GitHub Release, Scoop, and Homebrew having
+        # succeeded doesn't mean the release is fully done if WinGet
+        # didn't publish.
+        if: always() && steps.winget.outcome == 'failure'
+        run: |
+          echo "::error::WinGet publish failed — see the 'Publish to WinGet' step above. If casablanque-code.zt hasn't been submitted to microsoft/winget-pkgs yet, winget-releaser can't create the first entry; submit an initial manifest manually with wingetcreate, then this step will start succeeding on future releases."
+          exit 1