pi-chrome 0.15.13 → 0.15.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,10 @@
|
|
|
2
2
|
|
|
3
3
|
All notable user-facing changes to `pi-chrome`.
|
|
4
4
|
|
|
5
|
+
## 0.15.14 — 2026-05-14
|
|
6
|
+
|
|
7
|
+
- **Clearer consent wait state.** After the Chrome approval page opens, Pi now says “Approve or deny the Chrome approval page to continue” instead of looking stuck at the launch step.
|
|
8
|
+
|
|
5
9
|
## 0.15.13 — 2026-05-14
|
|
6
10
|
|
|
7
11
|
- **Fix Chrome-side consent hang.** `/chrome authorize` now launches the browser consent page as a short command, then polls for the decision. This avoids holding one long extension command open while the user reads/clicks the page, which could leave Pi stuck at “Opening Chrome approval page…”.
|
|
@@ -636,6 +636,7 @@ Usage rules:
|
|
|
636
636
|
ctx.ui.notify("Chrome approval failed: companion extension could not open the consent page.", "warning");
|
|
637
637
|
return;
|
|
638
638
|
}
|
|
639
|
+
ctx.ui.notify("Approve or deny the Chrome approval page to continue.", "info");
|
|
639
640
|
|
|
640
641
|
const deadline = Date.now() + (request.timeoutMs ?? 5 * 60_000);
|
|
641
642
|
while (Date.now() < deadline + 2_000) {
|