gh-glance 0.13.1 → 0.13.2

package/CHANGELOG.md

@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.13.2] - 2026-09-07
+
+### Fixed
+
+- **"Upgrade waiting for legacy quota reset" could never clear.** A pane holding
+  a pre-0.12.0 ledger with unsettled GraphQL charges waited on a deadline that
+  did not exist, so the message stayed for as long as that file was present --
+  weeks, in one case, long after the quota windows it was waiting for had ended.
+  Migrating such a ledger deliberately drops its budgets, because their numbers
+  came from `/rate_limit` and were never spendable capacity; the reset times
+  recorded alongside them are still facts about when those windows closed, and
+  are now read as the deadline they always were. Reading a reset is not the same
+  as spending against it. Affected panes clear themselves on the next launch.
+
 ## [0.13.1] - 2026-09-07
 
 ### Fixed
@@ -926,7 +940,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.1...HEAD
+[Unreleased]: https://github.com/juan294/gh-glance/compare/v0.13.2...HEAD
+[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
 [0.12.0]: https://github.com/juan294/gh-glance/compare/v0.11.2...v0.12.0

package/index.mjs

@@ -2528,7 +2528,19 @@ function inspectLegacyMigration(root, state, now) {
       const uncertain = Object.values(legacy.reservations).some((reservation) =>
         ["started", "completed"].includes(reservation.status) && reservationCost(reservation, resource, legacy.leases, now) > 0);
       if (uncertain) {
-        const reset = budget?.resetMs;
+        // The deadline may only be read from the migrated view for resources the
+        // migration kept. A v1 file's budgets are dropped on purpose -- they came
+        // from /rate_limit and are not spendable capacity -- but the reset they
+        // record is still a fact about when that window ended, and using it as a
+        // deadline is not the same as admitting work against it. Core already had
+        // a reconstruction above; GraphQL never did, so a v1 file holding any
+        // uncertain GraphQL charge asked a dropped budget for its reset, found
+        // none, and reported legacy-unresolved -- which has no deadline and so
+        // never cleared. The file it came from had a perfectly good reset in it
+        // the whole time.
+        const reset = Number.isFinite(budget?.resetMs)
+          ? budget.resetMs
+          : Number(raw?.budgets?.[resource]?.resetMs);
         if (!Number.isFinite(reset)) return { ok: false, reason: "legacy-unresolved" };
         holdUntil = Math.max(holdUntil, reset + BUDGET_RESET_GRACE_MS);
       }

package/package.json

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