瀏覽代碼

Drop MacOS-13 cli support (#11169)

Chris Estreich 1 周之前
父節點
當前提交
1c7ccb7b3d
共有 2 個文件被更改,包括 3 次插入7 次删除
  1. 1 5
      .github/workflows/cli-release.yml
  2. 2 2
      apps/cli/README.md

+ 1 - 5
.github/workflows/cli-release.yml

@@ -23,9 +23,6 @@ jobs:
           - os: macos-latest
             platform: darwin-arm64
             runs-on: macos-latest
-          - os: macos-13
-            platform: darwin-x64
-            runs-on: macos-13
           - os: ubuntu-latest
             platform: linux-x64
             runs-on: ubuntu-latest
@@ -331,7 +328,7 @@ jobs:
           echo "## Requirements" >> "$NOTES_FILE"
           echo "" >> "$NOTES_FILE"
           echo "- Node.js 20 or higher" >> "$NOTES_FILE"
-          echo "- macOS (Intel or Apple Silicon) or Linux x64" >> "$NOTES_FILE"
+          echo "- macOS Apple Silicon (M1/M2/M3/M4) or Linux x64" >> "$NOTES_FILE"
           echo "" >> "$NOTES_FILE"
           echo "## Usage" >> "$NOTES_FILE"
           echo "" >> "$NOTES_FILE"
@@ -347,7 +344,6 @@ jobs:
           echo "" >> "$NOTES_FILE"
           echo "This release includes binaries for:" >> "$NOTES_FILE"
           echo '- `roo-cli-darwin-arm64.tar.gz` - macOS Apple Silicon (M1/M2/M3)' >> "$NOTES_FILE"
-          echo '- `roo-cli-darwin-x64.tar.gz` - macOS Intel' >> "$NOTES_FILE"
           echo '- `roo-cli-linux-x64.tar.gz` - Linux x64' >> "$NOTES_FILE"
           echo "" >> "$NOTES_FILE"
           echo "## Checksums" >> "$NOTES_FILE"

+ 2 - 2
apps/cli/README.md

@@ -19,7 +19,7 @@ curl -fsSL https://raw.githubusercontent.com/RooCodeInc/Roo-Code/main/apps/cli/i
 **Requirements:**
 
 - Node.js 20 or higher
-- macOS (Intel or Apple Silicon) or Linux x64
+- macOS Apple Silicon (M1/M2/M3/M4) or Linux x64
 
 **Custom installation directory:**
 
@@ -259,7 +259,7 @@ To trigger a release:
 
 The workflow will:
 
-1. Build the CLI on all platforms (macOS Intel, macOS ARM, Linux x64)
+1. Build the CLI on all platforms (macOS Apple Silicon, Linux x64)
 2. Create platform-specific tarballs with bundled ripgrep
 3. Verify each tarball
 4. Create a GitHub release with all tarballs attached