Fix jq error when GitHub API returns object instead of array

- Add check to verify response is array before indexing with [0]
- Handle GitHub API error objects (rate limits, auth errors, etc.)
- Extract error messages from API response for better debugging
- Resolves "Cannot index object with number" jq error

Co-authored-by: shenxianpeng <[email protected]>

Author: Copilot

lib/utils.bash

@@ -50,11 +50,19 @@ fetch_all_assets() {
   response=$(curl -s -H "Accept: application/vnd.github.v3+json" \
     "https://api.github.com/repos/${GH_REPO}/releases")
 
-  # Check if response is valid JSON and has releases
+  # Check if response is valid JSON
   if ! echo "$response" | jq empty 2>/dev/null; then
     fail "Failed to fetch releases from GitHub API. Invalid JSON response."
   fi
 
+  # Check if response is an array (releases endpoint returns array)
+  if ! echo "$response" | jq -e 'type == "array"' >/dev/null 2>&1; then
+    # Response is not an array, likely an error from GitHub API
+    local error_message
+    error_message=$(echo "$response" | jq -r '.message // "Unknown API error"' 2>/dev/null || echo "API returned unexpected format")
+    fail "GitHub API error: ${error_message}. Please check your network connection and GitHub API status."
+  fi
+  
   # Check if there are any releases
   local release_count
   release_count=$(echo "$response" | jq 'length')