Add Capsule Local 0.1.1 dashboard update notice

CHANGELOG.md

@@ -9,6 +9,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- Capsule Local 0.1.1 displays “you have updated to 0.1.1” on the dashboard for manual installer upgrade testing.
+
 - TTP Capsule plugin publishing integration with bounded chunk uploads, JSON-compatible YAML metadata, public artifact verification, and single-range update downloads.
 - Windows x64 NSIS packaging with separate unsigned Capsule Local builds and signed public release builds. Release builds require an HTTPS feed and publisher identity; sessions remain outside the installation directory.
 - Main-process automatic update checks at startup and every four hours, background downloads, progress, manual checks, and explicit restart-to-install controls before and after sign-in. Duplicate checks are suppressed; failures remain retryable. Connected sites cannot choose an update feed or installer.

README.md

@@ -17,7 +17,7 @@ npm run dev
 
 ## Package and update
 
-`npm run dist:win` builds a per-user Windows x64 installer at `dist/local/Capsule-Local-0.1.0-x64-Setup.exe` (the filename follows the package version). This unsigned **Capsule Local** build has its own installation and session directory; automatic updates are disabled. `npm run pack:win` produces an unpacked app for inspection. `npm test` checks updater behavior and release validation.
+`npm run dist:win` builds a per-user Windows x64 installer at `dist/local/Capsule-Local-0.1.1-x64-Setup.exe` (the filename follows the package version). This unsigned **Capsule Local** build has its own installation and session directory; automatic updates are disabled. To update a 0.1.0 test installation, close Capsule Local and run the 0.1.1 installer under the same Windows account. Reopen it and confirm the dashboard says “you have updated to 0.1.1”; the installer preserves app data. This manual test does not publish to the signed release feed. `npm run pack:win` produces an unpacked app for inspection. `npm test` checks updater behavior and release validation.
 
 Public builds use `npm run release:win`, require a permanent HTTPS update URL and Windows signing identity, and go to `dist/release/`. They download updates in the background and offer **Restart to update**, including before sign-in. Closing the app normally does not install an update. A closed app checks after its next launch.
 

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "capsule",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "capsule",
-      "version": "0.1.0",
+      "version": "0.1.1",
       "license": "MIT",
       "dependencies": {
         "@electron-toolkit/utils": "^4.0.0",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "capsule",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Desktop companion for The Tempus Project sites",
   "main": "./out/main/index.js",
   "author": "Joey Kimsey <Joey@thetempusproject.com>",

src/renderer/index.html

@@ -352,6 +352,7 @@
         <div class="m-2 m-lg-4">
           <div class="col-12 col-lg-10 mx-auto p-4 rounded shadow-sm context-main-bg">
             <h1 class="h3">Dashboard</h1>
+            <p class="alert alert-success" id="home-update-notice">you have updated to 0.1.1</p>
             <p class="text-muted" id="home-note"></p>
             <p class="mb-0">
               Connected to <a id="home-site" href="#" target="_blank" rel="noreferrer"></a>