sentry-tui 0.10.0 → 0.12.0

package/README.md

@@ -8,14 +8,14 @@ mirroring Sentry's real information architecture and screen layouts.
 Every destination in the current navigation opens a real screen across Issues,
 Explore, Dashboards, Seer, and Monitors — 30 in all, with no placeholder panes.
 
-| Area       | What's built                                                                                                                                        |
-| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Issues     | Query-backed views, saved views, cursor pagination, full event detail and stack traces, plus resolve, archive, bookmark, and review actions         |
-| Explore    | Traces, Logs, Metrics, Errors, Discover, Profiles, Replays, Releases, Conversations, saved queries, charts, and the trace query builder             |
-| Dashboards | All, Sentry Built, and starred dashboard lists, with a terminal widget grid for supported chart, table, number, and categorical widgets             |
-| Seer       | Ask Seer, conversation history, rich responses, and feature-gated Code Mode workflows                                                               |
-| Monitors   | Detector lists by type, check-in timelines, monitor detail, and Alerts workflows                                                                    |
-| App shell  | OAuth device-flow login, command palette, org and project switching, filters, Sentry URL navigation, telemetry, and self-updating compiled binaries |
+| Area       | What's built                                                                                                                                |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| Issues     | Query-backed views, saved views, cursor pagination, full event detail and stack traces, plus resolve, archive, bookmark, and review actions |
+| Explore    | Traces, Logs, Metrics, Errors, Discover, Profiles, Replays, Releases, Conversations, saved queries, charts, and the trace query builder     |
+| Dashboards | All, Sentry Built, and starred dashboard lists, with a terminal widget grid for supported chart, table, number, and categorical widgets     |
+| Seer       | Ask Seer, conversation history, rich responses, and feature-gated Code Mode workflows                                                       |
+| Monitors   | Detector lists by type, check-in timelines, monitor detail, and Alerts workflows                                                            |
+| App shell  | OAuth device-flow login, command palette, org and project switching, filters, Sentry URL navigation, telemetry, and in-process app updates  |
 
 Settings is intentionally left on sentry.io rather than mirrored as a stub.
 Most non-Issues data screens are read-only today. Next is deeper pagination,
@@ -24,7 +24,8 @@ tracked in the [open issues](https://github.com/billyvg/sentry-tui/issues).
 
 ## Install
 
-npm installs a self-contained binary — no Bun or Node needed at runtime.
+npm installs a compiled runtime host and a platform-neutral app payload — no
+Bun installation is needed at runtime.
 
 ```bash
 # one-off, or installed globally
@@ -32,23 +33,32 @@ npx sentry-tui
 npm install -g sentry-tui
 ```
 
-`sentry-tui` and `@billyvg/sentry-tui` are the same package; the platform
-binary arrives as an optional dependency, so you download one binary rather
-than four. Binaries are also attached to every
+`sentry-tui` and `@billyvg/sentry-tui` are the same package; the platform host
+arrives as an optional dependency, so you download one binary rather than
+four. The replaceable app payload is shared by every platform. Complete host
+and payload bundles are also attached to every host
 [release](https://github.com/billyvg/sentry-tui/releases).
 
 The npm install **keeps itself current**. Launching starts the app
-immediately on the build you already have, and a background process fetches
-anything newer — so a release reaches you without `npm i -g` again, and
-without ever making you wait on a 24MB download. Nothing about starting the
-app touches the network.
-
-When a new build has finished downloading, a bold pink **Update** appears in
-the bottom-left corner. Click it or press `U` and the app restarts into it on
-the spot; ignore it and you get the new version next launch either way. The
-app looks again every 15 minutes while it is open, and only ever offers a build
-it
-has already downloaded.
+immediately on what you already have, and a background process fetches any
+newer app payload — so a release reaches you without `npm i -g` again and
+without waiting on a full native binary. Nothing about starting the app
+touches the network.
+
+When a new payload has finished downloading, a bold pink **Update** appears in
+the bottom-left corner. Click it or press `U` and the long-lived host swaps the
+app tree while keeping the process, terminal mode, renderer, and React root
+alive. The app looks again every 15 minutes while it is open and only offers
+bytes already on disk. A release that changes the host/payload API falls back
+to the verified full-host restart path; a host-only fix is discovered through
+the same independent check and offered as a restart. Routine UI and application
+changes do not replace the host.
+
+The payload swap remounts the application tree, but keeps the open organization,
+screen, detail stack, filters, cursor, project selections, and active Seer run.
+Fetched API bodies are deliberately reloaded by the new payload rather than
+serialized. The long-lived host only carries a bounded, versioned JSON snapshot
+between the two app versions; schema validation and migrations belong to the app.
 
 Set `SENTRY_TUI_NO_UPDATE=1` to pin whatever you have; `CI` is treated the same
 way. A binary downloaded by hand from the releases page never updates itself,
@@ -101,22 +111,6 @@ Use `--no-browser` to print the URL instead of opening one, and `SENTRY_URL` +
 `SENTRY_CLIENT_ID` to log in to a self-hosted install (needs Sentry ≥ 26.1.0 and
 a **public** OAuth application from Settings → Account → API → Applications).
 
-### Personal token instead
-
-Create one at <https://sentry.io/settings/account/api/auth-tokens/> with these
-scopes — the same set `login` requests:
-
-```
-org:read  project:read  event:read  event:write  member:read  team:read
-```
-
-```bash
-export SENTRY_AUTH_TOKEN=sntryu_…
-```
-
-Resolution order is `SENTRY_AUTH_TOKEN` → `SENTRY_TOKEN` → the credential file.
-Environment tokens are used exactly as given and never refreshed.
-
 ### Files
 
 | Path                                    | Holds                                           |

package/package.json

@@ -11,7 +11,7 @@
     "url": "https://github.com/billyvg/sentry-tui/issues"
   },
   "name": "sentry-tui",
-  "version": "0.10.0",
+  "version": "0.12.0",
   "keywords": [
     "sentry",
     "tui",
@@ -34,6 +34,6 @@
     "node": ">=18.0.0"
   },
   "dependencies": {
-    "@billyvg/sentry-tui": "0.10.0"
+    "@billyvg/sentry-tui": "0.12.0"
   }
 }