@mcptask/cli 0.3.32 → 0.3.33
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
|
@@ -53,6 +53,20 @@ Once installed any way, it updates itself:
|
|
|
53
53
|
mcptask_runner update --self
|
|
54
54
|
```
|
|
55
55
|
|
|
56
|
+
## The scheduled job
|
|
57
|
+
|
|
58
|
+
npm keeps the binary in its cache (`npx`) or in `node_modules`, and deletes both
|
|
59
|
+
on its own schedule — `npm cache clean`, the next version fetched, `npm ci`. A
|
|
60
|
+
job pointing there would stop working the morning after. So when `init` writes a
|
|
61
|
+
scheduled job, it first copies the binary to `~/.mcptask/bin/mcptask_runner`
|
|
62
|
+
(`%USERPROFILE%\.mcptask\bin\mcptask_runner.exe` on Windows) and the job runs
|
|
63
|
+
that copy. It says so in its output. That copy is shared by every project on the
|
|
64
|
+
machine whose job runs it, and it is the one to keep current:
|
|
65
|
+
|
|
66
|
+
```bash
|
|
67
|
+
~/.mcptask/bin/mcptask_runner update --self
|
|
68
|
+
```
|
|
69
|
+
|
|
56
70
|
## Environment
|
|
57
71
|
|
|
58
72
|
| Variable | Effect |
|
package/package.json
CHANGED