@signalridge/pi-welcome 1.3.1 → 1.3.4

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
@@ -1,5 +1,26 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.3.4
4
+ ### Patch Changes
5
+
6
+ - 07350d4: Use the theme's `borderAccent` color for extension-owned outer borders so the popup and welcome-card framing follows the purple Signalridge palette.
7
+
8
+ ## 1.3.3
9
+ ### Patch Changes
10
+
11
+ - f714ea0: Publish the package versions already prepared by the previous release transition after its first publish attempt was blocked before npm publication.
12
+
13
+ ## 1.3.2
14
+ ### Patch Changes
15
+
16
+ - b6cf242: Peer dependency ranges now name the versions actually validated against, so an untested host combination fails at install time instead of silently at runtime: `@earendil-works/pi-coding-agent`, `pi-ai`, `pi-tui`, and `pi-agent-core` move from `"*"` to `^0.84.0`, and `typebox` from `"*"` to `^1.3.11`.
17
+
18
+ Shared dependencies now carry ONE declared range across every package that uses them, and `bun run check:shared-deps` keeps it that way.
19
+
20
+ `@narumitw/pi-tui-kit` was declared at three disjoint floors — `^0.54.0`, `^0.51.0`, and `^0.49.1` across nine packages — and the lockfile duly resolved three copies (0.54.0, 0.51.0, 0.49.3) installed side by side. For a shared rendering surface drawing into one terminal inside one host process, that means a theme rendering one way in one extension and another way in the next, with nothing failing at install to say so. All nine now declare `^0.54.0` and the install resolves a single copy. `@sinclair/typebox` likewise converges on `^0.34.50`.
21
+
22
+ The new check covers `dependencies` and `peerDependencies` and compares range strings rather than their semantics: two ranges that merely overlap are still a finding, because the goal is one intentional answer per dependency rather than an accidental intersection. `devDependencies` are deliberately out of scope — a build tool is not a shared surface, and `pi-subagents` intentionally carries its own toolchain. `docs/package-boundaries.md` documents the Kit as a shared surface for the first time.
23
+
3
24
  ## 1.3.1
4
25
  ### Patch Changes
5
26
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@signalridge/pi-welcome",
3
- "version": "1.3.1",
3
+ "version": "1.3.4",
4
4
  "description": "Startup resource and repository summary card for Pi.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -9,8 +9,8 @@
9
9
  "lifecycle": "stable"
10
10
  },
11
11
  "peerDependencies": {
12
- "@earendil-works/pi-coding-agent": "*",
13
- "@earendil-works/pi-tui": "*"
12
+ "@earendil-works/pi-coding-agent": "^0.84.0",
13
+ "@earendil-works/pi-tui": "^0.84.0"
14
14
  },
15
15
  "pi": {
16
16
  "extensions": [
package/src/index.ts CHANGED
@@ -432,7 +432,7 @@ export class WelcomeCard implements Component {
432
432
  if (safeWidth < MIN_WIDTH) return this.renderCompact(safeWidth);
433
433
 
434
434
  const t = this.theme;
435
- const border = (text: string) => t.fg("border", text);
435
+ const border = (text: string) => t.fg("borderAccent", text);
436
436
  const inner = safeWidth - 2;
437
437
  const line = (content: string) => border("│") + this.fit(content, inner) + border("│");
438
438
  const blank = () => line("");