@plannotator/pi-extension 0.28.32 → 0.28.33

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/README.md CHANGED
@@ -41,8 +41,10 @@ itself before loading the extension.
41
41
 
42
42
  Run Pi on **Node 22.23.4+, 24.22.1+ or 26.12.1+**. These October 2026 security
43
43
  releases stop trusting the compromised eMudhra certificate chain. On an older
44
- Node, HTTPS calls made inside Pi still trust it. The package's `engines` field
45
- states this floor; npm warns but does not block the install.
44
+ Node, HTTPS calls made inside Pi still trust it, and the extension says so once
45
+ when Pi starts (on Bun: Bun 1.4.4+). The package declares no `engines` floor on
46
+ purpose: npm passes over a release whose floor the running Node misses, which
47
+ kept older-Node installs on an old Plannotator without a word.
46
48
 
47
49
  Pi 0.79 introduced project trust for repository-local inputs. In interactive
48
50
  sessions, Pi asks before loading project settings, instructions, resources, and
package/index.ts CHANGED
@@ -35,6 +35,7 @@ import {
35
35
  } from "./generated/checklist.ts";
36
36
  import { loadConfig, resolveAgentTool, resolveUseJina } from "./generated/config.ts";
37
37
  import { detectPiHost, setPiHost } from "./pi-host.ts";
38
+ import { warnRuntimeTlsOnce } from "./runtime-tls.ts";
38
39
  import { importFresh, isPlannotatorUpdatedError, launchFailureText } from "./package-version.ts";
39
40
  import { readImprovementHook } from "./generated/improvement-hooks.ts";
40
41
  import { composeImproveContext } from "./generated/pfm-reminder.ts";
@@ -2645,6 +2646,9 @@ Call ${PLAN_MARK_DONE_TOOL} immediately after each completed step and before the
2645
2646
  for (const warning of loadedConfig.warnings) {
2646
2647
  ctx.ui.notify(`Plannotator config: ${warning}`, "warning");
2647
2648
  }
2649
+ // A runtime without the Oct 2026 TLS fixes: one line per Pi start. It
2650
+ // replaces the package's engines floor, which kept updates from installing (#902).
2651
+ warnRuntimeTlsOnce((message) => ctx.ui.notify(message, "warning"));
2648
2652
 
2649
2653
  // Check --plan flag
2650
2654
  if (pi.getFlag("plan") === true) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plannotator/pi-extension",
3
- "version": "0.28.32",
3
+ "version": "0.28.33",
4
4
  "type": "module",
5
5
  "description": "Plannotator Pi extension - interactive plan review with annotations, annotate agent messages, and review code/PRs",
6
6
  "author": "backnotprop",
@@ -44,6 +44,7 @@
44
44
  "plannotator-tool-host.ts",
45
45
  "session-opened.ts",
46
46
  "pi-host.ts",
47
+ "runtime-tls.ts",
47
48
  "package-version.ts",
48
49
  "inbox.ts",
49
50
  "server.ts",
@@ -75,9 +76,7 @@
75
76
  "peerDependencies": {
76
77
  "@earendil-works/pi-coding-agent": ">=0.79.1"
77
78
  },
78
- "engines": {
79
- "node": ">=22.23.4 <23 || >=24.22.1 <25 || >=26.12.1"
80
- },
79
+ "//engines": "No engines field on purpose (#902): for a bare or range install npm passes over a release whose engines the running Node misses, so Pi on an older Node silently stayed on an old Plannotator. runtime-tls.ts warns once per start instead. package-engines.test.ts fails if a node engines field comes back.",
81
80
  "devDependencies": {
82
81
  "glimpseui": "^0.8.0",
83
82
  "@earendil-works/pi-coding-agent": ">=0.79.1",