Skip to content

Commit 525376a

Browse files
Copilotalexec
andcommitted
Remove automatic README version update from release workflow
Co-authored-by: alexec <1142830+alexec@users.noreply.github.com>
1 parent 4df3e68 commit 525376a

2 files changed

Lines changed: 9 additions & 36 deletions

File tree

.github/workflows/release.yml

Lines changed: 0 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -19,30 +19,6 @@ jobs:
1919
token: ${{ secrets.GITHUB_TOKEN }}
2020
- run: git fetch --force --tags
2121

22-
- name: Update README version
23-
run: |
24-
# Checkout main branch to commit changes
25-
git checkout main
26-
27-
# Update README with the new version
28-
./scripts/update-readme-version.sh ${{ github.ref_name }}
29-
30-
# Configure git
31-
git config user.name "github-actions[bot]"
32-
git config user.email "github-actions[bot]@users.noreply.github.com"
33-
34-
# Commit and push if there are changes
35-
git add README.md
36-
if ! git diff --staged --quiet; then
37-
git commit -m "Update README to version ${{ github.ref_name }}"
38-
git push origin main
39-
else
40-
echo "No changes to README.md"
41-
fi
42-
43-
# Checkout the tag again for the build
44-
git checkout ${{ github.ref_name }}
45-
4622
- name: Set up Go
4723
uses: actions/setup-go@v3
4824
with:

README.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -268,21 +268,18 @@ Example MCP client configuration:
268268

269269
### Releasing a New Version
270270

271-
When you push a new tag (e.g., `v0.0.3`), the GitHub Actions release workflow will automatically:
272-
273-
1. Update all version references in this README.md
274-
2. Commit the updated README back to the main branch
275-
3. Build binaries for all supported platforms
276-
4. Create a GitHub release with the built binaries and checksums
277-
278271
To create a new release:
279272

280-
```bash
281-
git tag v0.0.3
282-
git push origin v0.0.3
283-
```
273+
1. Update version references in README.md (installation instructions)
274+
2. Create and push a tag:
275+
```bash
276+
git tag v0.0.3
277+
git push origin v0.0.3
278+
```
284279

285-
The README will be automatically updated with the new version number in all installation instructions.
280+
The GitHub Actions release workflow will automatically:
281+
- Build binaries for all supported platforms
282+
- Create a GitHub release with the built binaries and checksums
286283

287284
## License
288285

0 commit comments

Comments
 (0)