chore(release): bump client version to 1.1.0-alpha.3 (#1279)

The server takes its version from the tag via ldflags, but the client's is
pinned in package.json, tauri.conf.json and Cargo.toml. Without this bump the
v1.1.0-alpha.3 tag would build an installer still identifying as alpha.2, and
the client updater compares that string against the server's manifest — so a
stale value means clients never see the update.

Lockfiles follow (npm + cargo); README's build examples updated to match.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
J3vb
2026-07-30 19:33:30 +02:00
committed by GitHub
co-authored by Claude Opus 5
parent 8b07d33c2a
commit 4959e2fa40
6 changed files with 8 additions and 8 deletions
+2 -2
View File
@@ -136,11 +136,11 @@ Two main components:
```bash
# Server (Windows)
cd Server
go build -o chatserver.exe -ldflags "-s -w -X main.version=1.1.0-alpha.2" .
go build -o chatserver.exe -ldflags "-s -w -X main.version=1.1.0-alpha.3" .
# Server (Linux)
cd Server
CGO_ENABLED=0 go build -o chatserver -ldflags "-s -w -X main.version=1.1.0-alpha.2" .
CGO_ENABLED=0 go build -o chatserver -ldflags "-s -w -X main.version=1.1.0-alpha.3" .
# Client
cd Client/tauri-client