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>

Client/tauri-client/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "owncord-client",
-  "version": "1.1.0-alpha.2",
+  "version": "1.1.0-alpha.3",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "owncord-client",
-      "version": "1.1.0-alpha.2",
+      "version": "1.1.0-alpha.3",
       "dependencies": {
         "@jitsi/rnnoise-wasm": "^0.2.1",
         "@tauri-apps/api": "^2.10.1",

Client/tauri-client/package.json

@@ -1,7 +1,7 @@
 {
   "name": "owncord-client",
   "private": true,
-  "version": "1.1.0-alpha.2",
+  "version": "1.1.0-alpha.3",
   "type": "module",
   "scripts": {
     "dev": "vite",

Client/tauri-client/src-tauri/Cargo.lock

@@ -3106,7 +3106,7 @@ dependencies = [
 
 [[package]]
 name = "owncord-client"
-version = "1.1.0-alpha.2"
+version = "1.1.0-alpha.3"
 dependencies = [
  "device_query",
  "futures-util",

Client/tauri-client/src-tauri/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "owncord-client"
-version = "1.1.0-alpha.2"
+version = "1.1.0-alpha.3"
 edition = "2021"
 # Effective minimum: tauri 2.11 declares rust-version = "1.77.2", so the crate
 # cannot build below it. Declaring it here enables Cargo's MSRV-aware resolver

Client/tauri-client/src-tauri/tauri.conf.json

@@ -1,6 +1,6 @@
 {
   "productName": "OwnCord",
-  "version": "1.1.0-alpha.2",
+  "version": "1.1.0-alpha.3",
   "identifier": "com.owncord.client",
   "build": {
     "frontendDist": "../dist",