Update .gitea/workflows/ci.yml

.gitea/workflows/ci.yml

@@ -46,8 +46,10 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-cargo-build-target-
       
-      # 🔍 Check only crates under bin/
+      # 👇 Don't fail CI on hero-runner's warnings
       - name: Check code (all crates under bin/)
+        env:
+          RUSTFLAGS: "--cap-lints=warn"
         run: |
           set -euo pipefail
           find bin -name Cargo.toml -print0 | while IFS= read -r -d '' manifest; do
@@ -55,8 +57,10 @@ jobs:
             cargo check --manifest-path "$manifest" --verbose
           done
       
-      # ✅ Run tests only for crates under bin/
+      # 👇 Same trick for tests, otherwise they’d fail for the same reason
       - name: Run tests (all crates under bin/)
+        env:
+          RUSTFLAGS: "--cap-lints=warn"
         run: |
           set -euo pipefail
           find bin -name Cargo.toml -print0 | while IFS= read -r -d '' manifest; do
@@ -64,7 +68,8 @@ jobs:
             cargo test --manifest-path "$manifest" --verbose
           done
       
-      # 🧹 Clippy only for crates under bin/
+      # Clippy stays strict (still uses -D warnings for clippy lints).
+      # If this later fails because of hero-runner, we can also add RUSTFLAGS here.
       - name: Run clippy (all crates under bin/)
         run: |
           set -euo pipefail
@@ -73,11 +78,10 @@ jobs:
             cargo clippy --manifest-path "$manifest" -- -D warnings
           done
       
-      # Formatting can safely stay workspace-wide
       - name: Check formatting
         run: cargo fmt --all -- --check
       
-      # 🏗 Build release binaries only for crates under bin/
+      # Build was already succeeding; leaving it without cap-lints is fine.
       - name: Build release binaries (all crates under bin/)
         run: |
           set -euo pipefail