Release v0.1.11

- add a --version/-V/version flag (works without a TTY, used by the
  desktop's check_backend probe and the new CI guard)
- release workflows now verify the built binary's version matches the
  tag / dispatch version before publishing, preventing a repeat of the
  v0.1.10 mislabeled-binary release
- bump version to 0.1.11

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: gaoyu06

.github/workflows/release-macos.yml

@@ -35,6 +35,25 @@ jobs:
       - name: Build release binary
         run: cargo build --release --target ${{ matrix.target.rust_target }}
 
+      # Guard against the v0.1.10 incident: the npm package version is stamped
+      # from the tag / dispatch input, so a binary built from a checkout whose
+      # Cargo.toml wasn't bumped would ship mislabeled — and its self-update
+      # check would nag users forever. Fail the release instead.
+      - name: Verify binary version matches the release version
+        shell: bash
+        run: |
+          if [ "${GITHUB_EVENT_NAME}" = "workflow_dispatch" ]; then
+            expected="${{ inputs.release_version }}"
+          else
+            expected="${GITHUB_REF_NAME#v}"
+          fi
+          actual="$(./target/${{ matrix.target.rust_target }}/release/jucode --version | awk '{print $NF}')"
+          echo "expected=${expected} actual=${actual}"
+          if [ "${actual}" != "${expected}" ]; then
+            echo "::error::built binary reports ${actual} but the release is ${expected} — bump Cargo.toml (and commit) before tagging"
+            exit 1
+          fi
+
       - name: Stage artifact
         shell: bash
         run: |

.github/workflows/release.yml

@@ -36,6 +36,25 @@ jobs:
       - name: Build release binary
         run: cargo build --release --target ${{ matrix.target.rust_target }}
 
+      # Guard against the v0.1.10 incident: the npm package version is stamped
+      # from the tag / dispatch input, so a binary built from a checkout whose
+      # Cargo.toml wasn't bumped would ship mislabeled — and its self-update
+      # check would nag users forever. Fail the release instead.
+      - name: Verify binary version matches the release version
+        shell: bash
+        run: |
+          if [ "${GITHUB_EVENT_NAME}" = "workflow_dispatch" ]; then
+            expected="${{ inputs.release_version }}"
+          else
+            expected="${GITHUB_REF_NAME#v}"
+          fi
+          actual="$(./target/${{ matrix.target.rust_target }}/release/${{ matrix.target.binary_name }} --version | awk '{print $NF}')"
+          echo "expected=${expected} actual=${actual}"
+          if [ "${actual}" != "${expected}" ]; then
+            echo "::error::built binary reports ${actual} but the release is ${expected} — bump Cargo.toml (and commit) before tagging"
+            exit 1
+          fi
+
       - name: Stage artifact
         shell: bash
         run: |

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "jucode-cli"
-version = "0.1.10"
+version = "0.1.11"
 edition = "2021"
 
 [[bin]]

Cargo.toml

@@ -58,6 +58,14 @@ impl TuiRuntime for Runtime {
 fn main() -> io::Result<()> {
     jucode_agent_core::logging::init_global();
     let mut args = env::args().skip(1).collect::<Vec<_>>();
+    // Before anything that may touch the terminal: `--version` must work in
+    // TTY-less contexts (CI release guard, the desktop's check_backend probe).
+    if args.iter().any(|a| a == "--version" || a == "-V")
+        || args.first().map(String::as_str) == Some("version")
+    {
+        println!("jucode {}", env!("CARGO_PKG_VERSION"));
+        return Ok(());
+    }
     let approval_mode = match take_approval_mode_flag(&mut args) {
         Ok(mode) => mode,
         Err(error) => {