pi-tokenburn 0.5.5 → 0.5.7

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 +9 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -25,9 +25,15 @@ Totals match the `tokenburn` CLI exactly.
25
25
 
26
26
  ## Install
27
27
 
28
+ From npm:
29
+
28
30
  ```bash
29
31
  pi install npm:pi-tokenburn
30
- # or
32
+ ```
33
+
34
+ Or from git:
35
+
36
+ ```bash
31
37
  pi install git:github.com/sorinirimies/pi-tokenburn
32
38
  ```
33
39
 
@@ -158,6 +164,7 @@ bun install
158
164
  just check # typecheck + tests + pack check + nushell tests (what CI runs)
159
165
  just test # bun test only (with coverage)
160
166
  just coverage # tests + a coverage table
167
+ just push-all # push main to every configured remote (origin + the Gitea instances); `just --list` has pull-all, push-tags-all, release-all, the *-force and sync-gitea-* variants
161
168
  ```
162
169
 
163
170
  **Coverage:** every `bun test` collects coverage (`bunfig.toml`) and **fails below 95% lines / 95% functions**. CI shows the table on the run page and uploads `lcov.info`.
@@ -176,7 +183,7 @@ CI scripts are [nushell](https://www.nushell.sh) (`scripts/`), the same ones loc
176
183
 
177
184
  So library updates need no human: they are merged once CI passes, built, versioned and published as a patch. A downgrade, a failing check, or a major update stops the chain and waits for review.
178
185
 
179
- Manual release: `just bump patch` (or `minor` / `major` / `X.Y.Z`), then `just release-push`.
186
+ Manual release: `just release patch` (or `minor` / `major` / `X.Y.Z`) bumps, tags and pushes to GitHub; `just release-all patch` pushes to every configured remote; `just push-release-all` pushes an existing bump.
180
187
 
181
188
  **Secrets** (repo settings): `NPM_TOKEN` is an npm *granular access token* with publish rights and "bypass 2FA" (required for CI publishing). Optional: `GH_PAT` (lets a tag push trigger the release itself), `GITEA_TOKEN` (Gitea).
182
189
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-tokenburn",
3
- "version": "0.5.5",
3
+ "version": "0.5.7",
4
4
  "description": "Pi extension for live token usage monitoring and budget tracking (Day / Week / Month / Total). 0 prompt tokens.",
5
5
  "keywords": ["pi-package", "pi-extension", "tokenburn", "tokens", "analytics", "budget", "stats"],
6
6
  "license": "MIT",
@@ -23,7 +23,7 @@
23
23
  "@earendil-works/pi-coding-agent": "*"
24
24
  },
25
25
  "devDependencies": {
26
- "@earendil-works/pi-coding-agent": "^1.1.0",
26
+ "@earendil-works/pi-coding-agent": "^1.2.0",
27
27
  "@types/bun": "^1.4.3",
28
28
  "typescript": "^7.0.2"
29
29
  }