From 2f3bdc73d23a7d283110f10b059f70afe81bfef5 Mon Sep 17 00:00:00 2001 From: vickydotbat Date: Thu, 2 Apr 2026 21:47:28 +0200 Subject: [PATCH] Ship Windows toolkit asset as exe --- .gitea/workflows/release-tool.yml | 8 ++++---- README.md | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.gitea/workflows/release-tool.yml b/.gitea/workflows/release-tool.yml index 69c9fd3..d38c1d7 100644 --- a/.gitea/workflows/release-tool.yml +++ b/.gitea/workflows/release-tool.yml @@ -51,13 +51,13 @@ jobs: exit 1 fi linux_archive="/tmp/sow-toolkit-linux-amd64-${TAG_NAME}.tar.gz" - windows_archive="/tmp/sow-toolkit-windows-amd64-${TAG_NAME}.zip" + windows_archive="/tmp/sow-toolkit-windows-amd64-${TAG_NAME}.exe" tar -czf "${linux_archive}" -C tools sow-toolkit - zip -j "${windows_archive}" "${windows_binary}" + cp "${windows_binary}" "${windows_archive}" echo "linux_archive=${linux_archive}" >> "$GITHUB_OUTPUT" echo "linux_asset_name=sow-toolkit-linux-amd64.tar.gz" >> "$GITHUB_OUTPUT" echo "windows_archive=${windows_archive}" >> "$GITHUB_OUTPUT" - echo "windows_asset_name=sow-toolkit-windows-amd64.zip" >> "$GITHUB_OUTPUT" + echo "windows_asset_name=sow-toolkit-windows-amd64.exe" >> "$GITHUB_OUTPUT" echo "tag=${TAG_NAME}" >> "$GITHUB_OUTPUT" - name: Create release and upload artifacts @@ -121,7 +121,7 @@ jobs: run: | rm -f \ "/tmp/sow-toolkit-linux-amd64-${TAG_NAME}.tar.gz" \ - "/tmp/sow-toolkit-windows-amd64-${TAG_NAME}.zip" \ + "/tmp/sow-toolkit-windows-amd64-${TAG_NAME}.exe" \ /tmp/gitea-release.json - name: Prune old releases (keep latest 1) diff --git a/README.md b/README.md index 15efe5a..1f3e70f 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ During development, sibling repositories can point at `../sow-tools/tools/sow-to This repo publishes: - `sow-toolkit-linux-amd64.tar.gz` -- `sow-toolkit-windows-amd64.zip` +- `sow-toolkit-windows-amd64.exe` Consumer repos can fetch those binaries into their local `tools/` directory with: