@caius_kong/ccusage-dashboard 0.2.1 → 0.2.2
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 +14 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -82,6 +82,20 @@ python3 lib/server.py --budget 300 # run server directly from the repo
|
|
|
82
82
|
node bin/ccusage-ui.js # same as the npx experience
|
|
83
83
|
```
|
|
84
84
|
|
|
85
|
+
## Releasing a new version
|
|
86
|
+
|
|
87
|
+
Releases are done entirely from the GitHub Actions tab (no local commands, full audit log):
|
|
88
|
+
|
|
89
|
+
1. Push your code changes to `main` as usual.
|
|
90
|
+
2. Go to **Actions → Publish to npm → Run workflow**.
|
|
91
|
+
3. Leave **Version** empty to auto-bump a patch, or type a semver (e.g. `1.2.3`).
|
|
92
|
+
4. The workflow bumps `package.json`, tags `v*`, pushes back to `main`, and publishes to npm.
|
|
93
|
+
|
|
94
|
+
You can also trigger it with the CLI:
|
|
95
|
+
```bash
|
|
96
|
+
gh workflow run "Publish to npm" # bumps patch
|
|
97
|
+
```
|
|
98
|
+
|
|
85
99
|
## License
|
|
86
100
|
|
|
87
101
|
MIT © Caius Kong
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@caius_kong/ccusage-dashboard",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.2",
|
|
4
4
|
"description": "One-command local dashboard for ccusage: today/week/month/custom cost by model, 30-day trend, monthly budget alert. Numbers straight from ccusage.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "commonjs",
|