pi-multikey 1.6.0 → 1.7.1

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.
Files changed (2) hide show
  1. package/README.md +0 -23
  2. package/package.json +6 -2
package/README.md CHANGED
@@ -151,29 +151,6 @@ Set `agentOverrides` in `settings.json` to the pool provider:
151
151
  - other errors → handed back to pi's own retry mechanism.
152
152
  - Only when every key is exhausted does it surface the 429 upward, letting pi's own backoff retry as a safety net (by then the earliest cooldown has usually expired).
153
153
 
154
- ## Releasing to npm
155
-
156
- A GitHub Action (`.github/workflows/release.yml`) auto-publishes to npm on tag push.
157
-
158
- 1. Bump the version in `package.json` (and commit).
159
- 2. Tag the commit — the tag must match the version, e.g. `v1.0.1`:
160
-
161
- ```bash
162
- git tag v1.0.1
163
- git push origin v1.0.1
164
- ```
165
-
166
- 3. The workflow verifies tag/version match, dry-runs `npm pack`, then publishes with
167
- [npm provenance](https://docs.npmjs.com/generating-provenance-statements).
168
-
169
- Setup (once):
170
-
171
- - Add an npm **automation** token with `publish` scope as the `NPM_TOKEN` secret
172
- in the repo's GitHub **Settings → Secrets and variables → Actions**.
173
- (An automation token, not your login token, so 2FA never blocks the action.)
174
- - The repo and package must be **public** for provenance to work.
175
- - Pre-release tags like `v1.0.1-beta.1` publish to the `next` dist-tag instead of `latest`.
176
-
177
154
  ## Security note
178
155
 
179
156
  Keys are stored in plaintext at `~/.pi/agent/multikey.json`; recommended:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-multikey",
3
- "version": "1.6.0",
3
+ "version": "1.7.1",
4
4
  "description": "One pi provider backed by many API keys: automatic 429 rotation, per-request key leases for concurrent subagents, and a /multikey management TUI",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -11,7 +11,11 @@
11
11
  "rate-limit",
12
12
  "429",
13
13
  "provider",
14
- "key-pool"
14
+ "key-pool",
15
+ "bai",
16
+ "b.ai",
17
+ "opencode",
18
+ "multiple"
15
19
  ],
16
20
  "license": "MIT",
17
21
  "repository": {