mcptask-rails-runner 0.3.31 → 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.
- checksums.yaml +4 -4
- data/CHANGELOG.md +42 -1
- data/README.md +8 -0
- data/lib/mcptask_rails_runner/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: b898f033e2dcf9af29c095682f0d637867ae7cfdd886876f4a8b43fdf0263e9b
|
|
4
|
+
data.tar.gz: 50f5c5c692329c52c9842d6b6d99911258a4a60a8301a82e9417e5b448338d5d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f24f5b17dd93143e7e948fe8b6d45c43a2a0b3224ef82532368cb15146a2c28f52e11dfbd0ddaf423b443160cfb7233cc5bee5aa093b1034882b506cbb7ce690
|
|
7
|
+
data.tar.gz: 79c9c91d1f1968de191c1b99a2d2045ce0c828e04a4b50efab2476c961ef6fe0683513278cec1a4a29e17cb7a92e19118cbcaf5026946afdef9fb8cc17633f88
|
data/CHANGELOG.md
CHANGED
|
@@ -9,12 +9,53 @@ release notes for the same tag.
|
|
|
9
9
|
|
|
10
10
|
Nothing yet.
|
|
11
11
|
|
|
12
|
+
## 0.3.33
|
|
13
|
+
|
|
14
|
+
Full binary notes in
|
|
15
|
+
[mcptask-releases v0.3.33](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.33).
|
|
16
|
+
|
|
17
|
+
**Upgrading takes two commands.** `mcptask_runner update --self` replaces the binary; then a bare `mcptask_runner update` in every project on the host, because the bundled `.claude/` assets changed (baseline_permissions.json). Run it while no runner is working that checkout. A runner idling in a wait keeps the old binary until its next task or a restart (`launchctl kill SIGTERM`, wait for the job to stop, then `kickstart` on macOS), so restart it.
|
|
18
|
+
|
|
19
|
+
- `mcptask_runner:install` and `:update` (through the binary, from the next
|
|
20
|
+
release) write `~/.mcptask_env.d/runner_path`, putting `~/.mcptask/bin` on
|
|
21
|
+
PATH for terminals and coding CLIs started by hand. README says so.
|
|
22
|
+
|
|
23
|
+
Binary changes carried by this version:
|
|
24
|
+
|
|
25
|
+
- A run the host refused is filed as a bug, not set aside quietly ([#13139](https://mcptask.online/jchsoft/tasks/13139))
|
|
26
|
+
- Test and CI logs stay readable when reads outside the project are blocked ([#13137](https://mcptask.online/jchsoft/tasks/13137))
|
|
27
|
+
- The end of the workday stops the next task, not just an empty queue ([#13076](https://mcptask.online/jchsoft/tasks/13076))
|
|
28
|
+
- Auto-squash no longer merges a pull request that no CI has passed ([#13089](https://mcptask.online/jchsoft/tasks/13089))
|
|
29
|
+
- A crash on a customer's runner files a bug piece in the customer's own project ([#13090](https://mcptask.online/jchsoft/tasks/13090))
|
|
30
|
+
- `mcptask_runner` on PATH for a coding CLI you start yourself ([#13123](https://mcptask.online/jchsoft/tasks/13123))
|
|
31
|
+
- A scheduled job set up through npx no longer points into npm's cache ([#13095](https://mcptask.online/jchsoft/tasks/13095))
|
|
32
|
+
- Elapsed times count the hours the Mac slept ([#13132](https://mcptask.online/jchsoft/tasks/13132))
|
|
33
|
+
- A piece name with braces no longer stops the day ([#13121](https://mcptask.online/jchsoft/tasks/13121))
|
|
34
|
+
- Adopting the bundle's runner now updates the binary the scheduled job runs ([#13133](https://mcptask.online/jchsoft/tasks/13133))
|
|
35
|
+
|
|
36
|
+
## 0.3.32
|
|
37
|
+
|
|
38
|
+
Full binary notes in
|
|
39
|
+
[mcptask-releases v0.3.32](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.32).
|
|
40
|
+
|
|
41
|
+
**Upgrading starts with one command.** `mcptask_runner update --self` replaces the binary. The bundled `.claude/` assets did not change, so nothing on that account asks for a bare `update` in the projects — the sections below say whether anything else does. A runner idling in a wait keeps the old binary until its next task or a restart (`launchctl kill SIGTERM`, wait for the job to stop, then `kickstart` on macOS), so restart it.
|
|
42
|
+
|
|
43
|
+
No wrapper changes.
|
|
44
|
+
|
|
45
|
+
Binary changes carried by this version:
|
|
46
|
+
|
|
47
|
+
- A second `bundle update` in one day is taken up too ([#12905](https://mcptask.online/jchsoft/tasks/12905))
|
|
48
|
+
- A refused push ends the task; it is no longer worked around ([#12903](https://mcptask.online/jchsoft/tasks/12903))
|
|
49
|
+
- An expired trial stops the runner with one line instead of spinning ([#12953](https://mcptask.online/jchsoft/tasks/12953), [#12967](https://mcptask.online/jchsoft/tasks/12967))
|
|
50
|
+
- A fan-out of subagents over one file is no longer killed as a loop ([#12966](https://mcptask.online/jchsoft/tasks/12966))
|
|
51
|
+
- `ollama launch` works again, and a CLI that cannot start says so ([#12965](https://mcptask.online/jchsoft/tasks/12965))
|
|
52
|
+
|
|
12
53
|
## 0.3.31
|
|
13
54
|
|
|
14
55
|
Full binary notes in
|
|
15
56
|
[mcptask-releases v0.3.31](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.31).
|
|
16
57
|
|
|
17
|
-
**Upgrading is
|
|
58
|
+
**Upgrading is two commands this once.** `mcptask_runner update --self` replaces the binary. Then a bare `mcptask_runner update` once in every project on the host (it also stamps the machine's helper home) — not because the bundled `.claude/` assets changed (they did not), but because this tag starts recording which version installed them, and until that record exists every run start prints a WARN and leaves the files alone; see "The installed skills and helpers follow the binary by themselves" below. From then on installing a new binary is enough. A runner idling in a wait keeps the old binary until its next task or a restart (`launchctl kill SIGTERM`, wait for the job to stop, then `kickstart` on macOS), so restart it.
|
|
18
59
|
|
|
19
60
|
No wrapper changes.
|
|
20
61
|
|
data/README.md
CHANGED
|
@@ -139,6 +139,14 @@ through PATH: the binary shares its name with the legacy tooling, and a PATH
|
|
|
139
139
|
lookup could pick up the wrong install. `MCPTASK_RUNNER_BIN` overrides both,
|
|
140
140
|
and install leaves `~/.mcptask/bin` untouched while it is set.
|
|
141
141
|
|
|
142
|
+
The gem ships no `mcptask_runner` executable of its own. What puts the name on
|
|
143
|
+
PATH for a person — or a coding CLI they start by hand, which the `pr` skill
|
|
144
|
+
asks to run `mcptask_runner pr …` — is `~/.mcptask_env.d/runner_path`, written
|
|
145
|
+
by install and update from the binary itself: it prepends `~/.mcptask/bin`, and
|
|
146
|
+
the shell startup file install configured sources it. Open a new terminal after
|
|
147
|
+
an install or update for it to apply. The wrapper still does not look the
|
|
148
|
+
binary up through PATH.
|
|
149
|
+
|
|
142
150
|
## Development
|
|
143
151
|
|
|
144
152
|
```bash
|
|
@@ -10,5 +10,5 @@ module McptaskRailsRunner
|
|
|
10
10
|
# Binary::INSTALL_DIR. So the pin is per project and per foreground rake
|
|
11
11
|
# invocation; the installed copy is per machine, and the newest binary any of
|
|
12
12
|
# those projects offers is the one that stays.
|
|
13
|
-
VERSION = "0.3.
|
|
13
|
+
VERSION = "0.3.33"
|
|
14
14
|
end
|