gh-glance 0.13.2 → 0.13.3

package/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.13.3] - 2026-09-07
+
+### Changed
+
+- **An upgrade hold now says whether it will clear or is stuck.** Two different
+  states shared the message `Upgrade waiting for legacy quota reset`: one has a
+  deadline and ends by itself, the other holds unsettled spend with no reset
+  recorded to wait for and never clears. The second now reads `Upgrade blocked:
+  older spend cannot be settled or waited out`, and the troubleshooting table
+  gives its recovery -- quit every pane and delete the leftover
+  `rate-governor-v1-*.json` files. Sharing one message meant a permanently
+  blocked pane looked like a temporary wait.
+
 ## [0.13.2] - 2026-09-07
 
 ### Fixed
@@ -940,7 +953,8 @@ engineering, security, QA and UX. What follows is what changed as a result.
 - The `main` field from `package.json`. It advertised the file as importable,
   but importing it took over the terminal or exited the host process.
 
-[Unreleased]: https://github.com/juan294/gh-glance/compare/v0.13.2...HEAD
+[Unreleased]: https://github.com/juan294/gh-glance/compare/v0.13.3...HEAD
+[0.13.3]: https://github.com/juan294/gh-glance/compare/v0.13.2...v0.13.3
 [0.13.2]: https://github.com/juan294/gh-glance/compare/v0.13.1...v0.13.2
 [0.13.1]: https://github.com/juan294/gh-glance/compare/v0.13.0...v0.13.1
 [0.13.0]: https://github.com/juan294/gh-glance/compare/v0.12.0...v0.13.0

package/README.md

@@ -711,7 +711,8 @@ GH_GLANCE_ICONS=ascii gh-glance
 | Repeated GitHub rate-limit messages | A classified rate-limit response is published as one shared resource block. Local panes make no data retry before that block's probe/reset deadline. Use `--doctor` to inspect the resource and reset; repeated manual refresh cannot override it. |
 | It exits immediately when piped | Intentional. It is a full-screen dashboard, not a reporting command. |
 | `Restart required: close older gh-glance panes` | A pane from an older release still holds a live lease in the previous coordination format, which this version cannot join. Quit those panes; this one resumes on its own. Nothing is killed for you, and no state needs deleting. |
-| `Upgrade waiting for legacy quota reset` | The older panes are gone, but left spend that cannot be proven settled. It waits for the affected rate-limit window to reset rather than assume the quota is free. |
+| `Upgrade waiting for legacy quota reset` | The older panes are gone, but left spend that cannot be proven settled. It waits for the affected rate-limit window to reset rather than assume the quota is free. This one has a deadline and clears itself. |
+| `Upgrade blocked: older spend cannot be settled or waited out` | The same unsettled spend, but the older file records no reset to wait for, so there is no deadline and it will not clear on its own. Quit every pane, then delete the `rate-governor-v1-*.json` files in the configuration directory -- they are the leftover evidence, and with no reset recorded there is nothing further to learn from them. Coordination starts clean on the next launch. |
 | `Coordination state unavailable; evidence preserved` | Coordination state could not be read and was deliberately not overwritten, so nothing is lost. Run `gh-glance --doctor` and check the config directory's permissions. |
 | `Shared HTTP request or cooldown in progress` | Panes share one outbound request slot and one cooldown. Another pane holds it, or a server-sent `Retry-After` is still running. Normal pacing, not an error. |
 | `Verified identity unavailable; waiting to retry` | The account behind your credential has not been confirmed yet -- not signed in, a denied or malformed proof, or a slow credential helper. Check `gh auth status`. Retries are rate-limited, so this clears on its own rather than immediately. |

package/index.mjs

@@ -3072,7 +3072,14 @@ function retryThrottledTransport(root, host, { now = Date.now } = {}) {
 
 function identityCoordinationMessage(reason) {
   if (reason === "restart-required") return "Restart required: close older gh-glance panes";
-  if (["migration-hold", "legacy-unresolved"].includes(reason)) return "Upgrade waiting for legacy quota reset";
+  // These two were one message for a long time, and the difference between them
+  // is the difference between waiting and being stuck. A migration hold has a
+  // deadline and ends by itself. An unresolved legacy ledger has no deadline at
+  // all -- it holds unsettled spend with no reset recorded to wait for -- so the
+  // same wording had people waiting weeks for something that was never going to
+  // arrive. Say which one it is.
+  if (reason === "migration-hold") return "Upgrade waiting for legacy quota reset";
+  if (reason === "legacy-unresolved") return "Upgrade blocked: older spend cannot be settled or waited out";
   if (["legacy-corrupt", "corrupt"].includes(reason)) return "Coordination state unavailable; evidence preserved";
   if (reason === "transport-busy") return "Shared HTTP request or cooldown in progress";
   if (reason === "throttle-paused") return "Paused after repeated rate limits; refresh to retry";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gh-glance",
-  "version": "0.13.2",
+  "version": "0.13.3",
   "description": "A live-refreshing GitHub dashboard for your terminal: Actions, Issues, Pull Requests, and Security alerts in one narrow pane",
   "type": "module",
   "bin": {