Fix prerelease flag for fork releases

Author: metyatech

.github/workflows/fork-release-windows.yml

@@ -28,6 +28,17 @@ jobs:
       - name: Install Rust (stable)
         uses: dtolnay/rust-toolchain@stable
 
+      - name: Compute prerelease flag
+        id: prerelease
+        shell: bash
+        run: |
+          set -euo pipefail
+          if [[ "${GITHUB_REF_NAME}" =~ ^fork-v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+            echo "is_prerelease=false" >> "$GITHUB_OUTPUT"
+          else
+            echo "is_prerelease=true" >> "$GITHUB_OUTPUT"
+          fi
+
       - name: Cargo build (release)
         shell: powershell
         run: |
@@ -48,5 +59,5 @@ jobs:
         with:
           name: ${{ github.ref_name }}
           tag_name: ${{ github.ref_name }}
-          prerelease: ${{ contains(github.ref_name, '-') }}
+          prerelease: ${{ steps.prerelease.outputs.is_prerelease == 'true' }}
           files: dist/*

docs/fork-release.md

@@ -11,6 +11,8 @@ This fork ships Windows `codex self-update` binaries via GitHub Releases.
    git push metyatech fork-v0.104.1
    ```
 
+   Pre-releases use a suffix after the `X.Y.Z` version (for example `fork-v0.104.1-alpha.1`).
+
 2. GitHub Actions builds Windows binaries and publishes a GitHub Release with assets:
    - `codex-x86_64-pc-windows-msvc.exe`
    - `codex-command-runner-x86_64-pc-windows-msvc.exe`