release: 2.8.0+linux.2

README.md

@@ -1,4 +1,4 @@
-# FrameForge — Warframe Companion `v2.8.0+linux.1`
+# FrameForge — Warframe Companion `v2.8.0+linux.2`
 
 A desktop companion for Warframe — live inventory, market prices, trading, timers, relic overlay, and riven analysis. Read-only, no game modification.
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "warframe-companion",
   "private": true,
-  "version": "2.8.0+linux.1",
+  "version": "2.8.0+linux.2",
   "type": "module",
   "scripts": {
     "dev": "vite",
@@ -10,18 +10,18 @@
     "tauri": "tauri"
   },
   "dependencies": {
-    "@tauri-apps/api": "^2",
-    "@tauri-apps/plugin-opener": "^2",
-    "react": "^19.1.0",
-    "react-dom": "^19.1.0"
+    "@tauri-apps/api": "^2.11.1",
+    "@tauri-apps/plugin-opener": "^2.5.4",
+    "react": "^19.2.8",
+    "react-dom": "^19.2.8"
   },
   "devDependencies": {
-    "@tauri-apps/cli": "^2",
-    "@types/react": "^19.1.8",
-    "@types/react-dom": "^19.1.6",
-    "@vitejs/plugin-react": "^4.6.0",
-    "terser": "^5.48.0",
+    "@tauri-apps/cli": "^2.11.4",
+    "@types/react": "^19.2.17",
+    "@types/react-dom": "^19.2.3",
+    "@vitejs/plugin-react": "^4.7.0",
+    "terser": "^5.49.0",
     "typescript": "~5.8.3",
-    "vite": "^7.0.4"
+    "vite": "^7.3.6"
   }
 }

scripts/bump-version.sh

@@ -0,0 +1,46 @@
+#!/usr/bin/env bash
+# Write a new version into every file that carries one, then verify they
+# agree. The version lives in five places with nothing tying them together:
+# package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json, the crate's
+# own entry in src-tauri/Cargo.lock, and the README title. check-version.sh
+# catches drift between the first three at release time; this script is how
+# they move in lockstep in the first place.
+set -euo pipefail
+
+if [ $# -ne 1 ]; then
+  echo "usage: $0 <version>   e.g. $0 2.8.0+linux.2" >&2
+  exit 1
+fi
+new="$1"
+
+# The fork's scheme is <upstream-semver>+linux.<n>; anything else is a typo
+# or an upstream version that forgot its build metadata.
+case "$new" in
+  [0-9]*.[0-9]*.[0-9]*+linux.[0-9]*) ;;
+  *)
+    echo "version must look like <upstream>+linux.<n>, e.g. 2.8.0+linux.2" >&2
+    exit 1
+    ;;
+esac
+
+root="$(dirname "$0")/.."
+
+# First occurrence only, mirroring how check-version.sh reads each file:
+# both JSON files carry other "version" keys further down (dependencies,
+# bundle sections) that must not be touched.
+sed -i "0,/\"version\": \".*\"/s//\"version\": \"$new\"/" "$root/package.json"
+sed -i "0,/\"version\": \".*\"/s//\"version\": \"$new\"/" "$root/src-tauri/tauri.conf.json"
+sed -i "0,/^version = \".*\"/s//version = \"$new\"/" "$root/src-tauri/Cargo.toml"
+
+# The README's title names the current release; the other versions in its
+# prose are worked examples and stay as written.
+sed -i "s/Companion \`v[^\`]*\`/Companion \`v$new\`/" "$root/README.md"
+
+# Resync the lock file's warframe-companion entry from the manifest. Offline:
+# only the workspace member's version changes, no dependency needs resolving.
+# Upstream once shipped a lock that lagged its manifest (v2.8.0); a --locked
+# build catches that only after this script has already prevented it.
+(cd "$root/src-tauri" && cargo update --workspace --offline --quiet)
+
+bash "$root/scripts/check-version.sh" "$new"
+grep -A1 'name = "warframe-companion"' "$root/src-tauri/Cargo.lock"