From 4df3e68ed86717f3fa07dcb20052c0f40bb81c72 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 17 Nov 2025 01:42:02 +0000
Subject: [PATCH 1/2] Initial plan


From 525376ae2a5e564e90277969acc2d9f76929ff7b Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 17 Nov 2025 01:45:15 +0000
Subject: [PATCH 2/2] Remove automatic README version update from release
 workflow

Co-authored-by: alexec <1142830+alexec@users.noreply.github.com>
---
 .github/workflows/release.yml | 24 ------------------------
 README.md                     | 21 +++++++++------------
 2 files changed, 9 insertions(+), 36 deletions(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index a2f2adb..05e2b3d 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -19,30 +19,6 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
       - run: git fetch --force --tags
 
-      - name: Update README version
-        run: |
-          # Checkout main branch to commit changes
-          git checkout main
-
-          # Update README with the new version
-          ./scripts/update-readme-version.sh ${{ github.ref_name }}
-
-          # Configure git
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-          # Commit and push if there are changes
-          git add README.md
-          if ! git diff --staged --quiet; then
-            git commit -m "Update README to version ${{ github.ref_name }}"
-            git push origin main
-          else
-            echo "No changes to README.md"
-          fi
-
-          # Checkout the tag again for the build
-          git checkout ${{ github.ref_name }}
-
       - name: Set up Go
         uses: actions/setup-go@v3
         with:
diff --git a/README.md b/README.md
index 1fb64ea..703f9de 100644
--- a/README.md
+++ b/README.md
@@ -268,21 +268,18 @@ Example MCP client configuration:
 
 ### Releasing a New Version
 
-When you push a new tag (e.g., `v0.0.3`), the GitHub Actions release workflow will automatically:
-
-1. Update all version references in this README.md
-2. Commit the updated README back to the main branch
-3. Build binaries for all supported platforms
-4. Create a GitHub release with the built binaries and checksums
-
 To create a new release:
 
-```bash
-git tag v0.0.3
-git push origin v0.0.3
-```
+1. Update version references in README.md (installation instructions)
+2. Create and push a tag:
+   ```bash
+   git tag v0.0.3
+   git push origin v0.0.3
+   ```
 
-The README will be automatically updated with the new version number in all installation instructions.
+The GitHub Actions release workflow will automatically:
+- Build binaries for all supported platforms
+- Create a GitHub release with the built binaries and checksums
 
 ## License