server-studio 1.2.5 → 1.2.6

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 Notable changes to Server Studio. Dates are release dates.
 
+## 1.2.6 — 2026-08-30
+
+- Documentation only. No runtime change; the code is identical to 1.2.5.
+- The README now says that anyone on **1.1.1 or older** has no update button, because the version
+  badge and the update check both arrived in 1.2.0. They update once with
+  `npm install -g server-studio` and the badge takes over from there. This is published as a release
+  because npm renders the README from the package, so the note was missing on the page most people
+  land on.
+- Removed a line that appeared twice.
+
 ## 1.2.5 — 2026-08-30
 
 ### The install counter is gone

package/README.md

@@ -195,14 +195,19 @@ which is what makes this safe to call from a build step.
 
 Run `server-studio add` with no arguments for the full list of fields.
 
-Run `server-studio add` with no arguments for the full list of fields.
-
 ### Staying up to date
 
 The version sits under the app name in the sidebar. When a newer release is on npm it turns green
 and becomes a button: click it, confirm, and the update runs in a terminal window. Restart Server
 Studio when it finishes. Your saved servers and folders are never touched by an update.
 
+Coming from **1.1.1 or older**? That badge did not exist yet, so there is no button in your copy.
+Update once by hand and every update after that is a click:
+
+```bash
+npm install -g server-studio
+```
+
 ### Backups
 
 **Export** saves your whole list to `server-studio-backup.json`. **Import** loads one back.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "server-studio",
-  "version": "1.2.5",
+  "version": "1.2.6",
   "description": "A tiny dashboard for your local dev servers. One click to run, stop and open them, with one permanent port per project.",
   "author": "Md Mahdi Hasan",
   "license": "MIT",