jb/harness-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: deploy published Pi extension packages

Browse Source
This commit is contained in:
jb
2026-09-01 18:02:16 -04:00
parent 72a1645fdb
commit 3b5a11c815
4 changed files with 39 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/npm-packages.md
+7 -7
View File
@@ -46,14 +46,14 @@ Publish `@jbcode/pi-shared` before a new version of any extension that depends o
## Install with Pi
After configuring the same scope and token in the npm configuration visible to Pi:
After configuring the same scope and token in the npm configuration visible to Pi, install the currently deployed release set with exact version pins:
```bash
pi install npm:@jbcode/pi-dictate
pi install npm:@jbcode/pi-file-search
pi install npm:@jbcode/pi-interactive-subagents
pi install npm:@jbcode/pi-native-hooks
pi install npm:@jbcode/pi-todo-herdr
pi install npm:@jbcode/pi-dictate@0.1.0
pi install npm:@jbcode/pi-effort-controls@0.1.0
pi install npm:@jbcode/pi-prompt-snippets@0.1.0
pi install npm:@jbcode/pi-interactive-subagents@3.7.2
pi install npm:@jbcode/pi-todo-herdr@0.2.5
```
Pi installs runtime dependencies from the same scoped registry. The repository's symlink-based development exposure remains controlled separately by `config/pi-links.json`.
Pi installs runtime dependencies from the same scoped registry. `config/pi-links.json` deliberately exposes no extension symlinks, preventing duplicate local and published copies.