@usepipa/pipa 0.6.0-beta.5 → 0.6.0
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 +11 -16
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -44,22 +44,18 @@ Want Lunch Pail Labs to set up and run agent workflows for your team? See [Pipa
|
|
|
44
44
|
**Runs on** macOS, Linux, and Windows. **Requires** Node.js 22 or newer, [OpenCode](https://opencode.ai) installed and authenticated, and a Slack workspace where you can create an app.
|
|
45
45
|
|
|
46
46
|
```sh
|
|
47
|
-
npm install --global @usepipa/pipa
|
|
47
|
+
npm install --global @usepipa/pipa@0.6.0
|
|
48
48
|
pipa init
|
|
49
49
|
pipa start
|
|
50
50
|
```
|
|
51
51
|
|
|
52
52
|
`pipa init` walks you through Slack setup and saves your profile under `~/.pipa`. Invite Pipa to an allowed channel and mention it. Follow the [four-minute setup video](https://www.youtube.com/watch?v=rlTMdkPWPcA) or the [written tutorial](https://www.usepipa.com/opencode-slack?utm_source=github&utm_medium=repo_readme&utm_campaign=signup&utm_content=readme_install_guide).
|
|
53
53
|
|
|
54
|
-
###
|
|
54
|
+
### OpenCode version selection
|
|
55
55
|
|
|
56
|
-
|
|
56
|
+
Pipa automatically detects OpenCode v1 or v2 and selects its native adapter. There is no manual Pipa migration command. OpenCode owns its data/schema upgrades; installing Pipa does not install or upgrade OpenCode.
|
|
57
57
|
|
|
58
|
-
|
|
59
|
-
npm install --global @usepipa/pipa@0.6.0-beta.5
|
|
60
|
-
```
|
|
61
|
-
|
|
62
|
-
Normal installs use npm's `latest` tag; later betas use `@beta`. This updates Pipa, not OpenCode. Before upgrading, stop Pipa and back up its profile. Keep your current OpenCode version initially. Do not rerun `pipa init` or start a second listener. Read the [beta release notes](https://github.com/lunchpaillola/pipa/blob/main/docs/beta-release.md) for limits and rollback steps.
|
|
58
|
+
Unversioned installs use npm's `latest` tag; `@beta` selects the beta channel. Before upgrading, stop/drain Pipa and back up its profile. Keep your current OpenCode version initially. Do not rerun `pipa init` or start a second listener. Read the [release notes](docs/release-0.6.0.md) for limits and rollback steps.
|
|
63
59
|
|
|
64
60
|
## Security model
|
|
65
61
|
|
|
@@ -80,7 +76,7 @@ Socket Mode connects Pipa to Slack through an outbound connection. You do not ne
|
|
|
80
76
|
1. Install Pipa:
|
|
81
77
|
|
|
82
78
|
```sh
|
|
83
|
-
npm install --global @usepipa/pipa
|
|
79
|
+
npm install --global @usepipa/pipa@0.6.0
|
|
84
80
|
```
|
|
85
81
|
|
|
86
82
|
2. From the folder where you want Pipa to work, run:
|
|
@@ -191,12 +187,12 @@ The picker shows up to 100 matches; narrow your search for more. A listed model
|
|
|
191
187
|
|
|
192
188
|
**An npm upgrade does not update your Slack app, register commands, or grant scopes.** Mentions and thread replies still work without the model command. Do not rerun `pipa init` or replace credentials to add it.
|
|
193
189
|
|
|
194
|
-
|
|
190
|
+
After verified publication, stop/drain Pipa and privately back up its profile before upgrading to `0.6.0`. Keep the current OpenCode version and use the same `PIPA_HOME` as your existing installation (leave it unset for the default `~/.pipa` profile):
|
|
195
191
|
|
|
196
192
|
```sh
|
|
197
|
-
npm install --global @usepipa/pipa@0.
|
|
193
|
+
npm install --global @usepipa/pipa@0.6.0
|
|
198
194
|
pipa --version
|
|
199
|
-
pipa manifest > "$HOME/pipa-slack-manifest-0.
|
|
195
|
+
pipa manifest > "$HOME/pipa-slack-manifest-0.6.0.json"
|
|
200
196
|
```
|
|
201
197
|
|
|
202
198
|
`pipa manifest` prints a local template without tokens. It does not change your profile or contact Slack. It is not an export of your app's current Slack settings.
|
|
@@ -204,14 +200,13 @@ pipa manifest > "$HOME/pipa-slack-manifest-0.5.6.json"
|
|
|
204
200
|
1. Open your **existing app** in [Slack App Management](https://api.slack.com/apps). Back up its current manifest.
|
|
205
201
|
2. Merge the desired `features.slash_commands` entries and add `commands` to `oauth_config.scopes.bot`. Keep existing settings, commands, scopes, Socket Mode, and interactivity. **Do not replace a customized Slack manifest with the local template.**
|
|
206
202
|
3. Save and reinstall or reauthorize the same app. Keep your tokens unless Slack rotates them. If it does, update the existing local config securely.
|
|
207
|
-
4.
|
|
203
|
+
4. Start the same stopped profile with its existing launch environment:
|
|
208
204
|
|
|
209
205
|
```sh
|
|
210
|
-
pipa
|
|
211
|
-
pipa restart --status
|
|
206
|
+
pipa start
|
|
212
207
|
```
|
|
213
208
|
|
|
214
|
-
Wait for
|
|
209
|
+
Wait for readiness, then try the registered model command. The absence of a startup warning does not prove the command is installed. Renaming the bot in Slack does not update Pipa's `botName` or command registration; keep them aligned and restart.
|
|
215
210
|
|
|
216
211
|
To try an unpublished branch, follow the isolated test-app steps in [CONTRIBUTING.md](CONTRIBUTING.md). Never start a second Socket listener with a running installation's credentials.
|
|
217
212
|
|