You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,7 @@ Run the executable — the widget appears in your taskbar.
49
49
50
50
-**Drag** the left divider to reposition the widget along the taskbar
51
51
-**Right-click** for a context menu with **Refresh**, **Update Frequency**, **Settings** (Start with Windows, Reset Position), and **Exit**
52
+
- Installations managed by WinGet defer upgrades to `winget upgrade` instead of replacing the executable in place
52
53
53
54
## Project structure
54
55
@@ -66,9 +67,7 @@ src/
66
67
67
68
Pre-built Windows executables are available on the [Releases](../../releases) page. Download `claude-code-usage-monitor.exe` and run it directly — no Rust toolchain required.
68
69
69
-
New releases are published automatically when a version tag is pushed:
70
+
After the GitHub Release is published, the release workflow also attempts to submit a WinGet manifest update for `CodeZeno.ClaudeCodeUsageMonitor`.
70
71
71
-
```bash
72
-
git tag v1.0.0
73
-
git push origin v1.0.0
74
-
```
72
+
- Configure a classic PAT as the `WINGETCREATE_GITHUB_TOKEN` repository secret with `public_repo` scope so `wingetcreate` can submit to `microsoft/winget-pkgs`
73
+
- The first WinGet submission still needs to be created manually; after the package exists, later tagged releases can update it automatically
0 commit comments