mcptask-rails-runner 0.3.4-aarch64-linux → 0.3.6-aarch64-linux
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 +50 -0
- data/lib/mcptask_rails_runner/version.rb +1 -1
- data/libexec/mcptask_runner +0 -0
- 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: d4e96e25efad05d447a3059eac285f3380183e6f63010235e65a9d1ff00b0d31
|
|
4
|
+
data.tar.gz: 0e2f6a5be99bdb086e22225e9d93b7951d7d96ce53bba2f97018072887b2a2af
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 7f4cbba698d0e599712e5887e601d83fa575c32b3d108baf19d81d5051beb94439954670addd1643aba35871314ac9a85214dec90a1726541880a724ed707a3b
|
|
7
|
+
data.tar.gz: 7aa8018eabdd68a1cbeaa36a1bc50f211d5cd819a4eab6437eaef9b4c42bde43a173dcb1e4c3ab567fa1fa5f563d617511239367f91d73b8969d7b69107512dc
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,56 @@ entries below describe wrapper changes only. Binary changes are listed in the
|
|
|
5
5
|
[mcptask-releases](https://github.com/jchsoft/mcptask-releases/releases)
|
|
6
6
|
release notes for the same tag.
|
|
7
7
|
|
|
8
|
+
## 0.3.6
|
|
9
|
+
|
|
10
|
+
No wrapper changes. Full notes in
|
|
11
|
+
[mcptask-releases v0.3.6](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.6).
|
|
12
|
+
|
|
13
|
+
- **The scheduled job stops running a binary its project has already replaced.**
|
|
14
|
+
`rake mcptask_runner:*` has always installed the gem's bundled binary over
|
|
15
|
+
`~/.mcptask/bin/mcptask_runner` when it was newer; the launchd/systemd job was
|
|
16
|
+
the one path that skipped it, because the generated launcher execs that
|
|
17
|
+
installed copy directly. An unattended host would pull main, run
|
|
18
|
+
`bundle install` while working a task, never call `mcptask_runner:update`, and
|
|
19
|
+
sit on a stale runner indefinitely. A scheduled run now reads the project's own
|
|
20
|
+
`Gemfile.lock`, and if it names a newer wrapper than the running binary, it
|
|
21
|
+
installs that gem's copy and re-runs on it.
|
|
22
|
+
|
|
23
|
+
This is not a download. The runner still never fetches a release on its own —
|
|
24
|
+
it only honours the version already merged and installed on purpose. Set
|
|
25
|
+
`MCPTASK_NO_ADOPT=1` to keep a host's binary pinned regardless.
|
|
26
|
+
|
|
27
|
+
Note the ordering: the already-installed binary is the one that decides whether
|
|
28
|
+
to adopt, so a host starts keeping itself current only once it is running 0.3.6
|
|
29
|
+
or later. Hosts on 0.3.5 and older need one `rake mcptask_runner:update` by hand
|
|
30
|
+
first.
|
|
31
|
+
|
|
32
|
+
## 0.3.5
|
|
33
|
+
|
|
34
|
+
No wrapper changes — this release carries a new binary. Full notes in
|
|
35
|
+
[mcptask-releases v0.3.5](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.5);
|
|
36
|
+
what a host running the scheduled job will notice:
|
|
37
|
+
|
|
38
|
+
- **A run that overflows its context now reports what it produced.** A task
|
|
39
|
+
whose pull request was already open was being called `error` with "task
|
|
40
|
+
exceeds token limit". That filed a bug piece for work that had shipped, and
|
|
41
|
+
because the quota decider stops a day on any error, one nearly-finished task
|
|
42
|
+
ended the rest of the day's runs. It now reports `overflow_pr_open`, the task
|
|
43
|
+
stays in progress, and the loop carries on to the next one.
|
|
44
|
+
- **The session that replaces an overflowed one is told how to survive.** The
|
|
45
|
+
in-process restart used to get one sentence of encouragement while the
|
|
46
|
+
cross-process handoff carried the whole context budget; both now get the same
|
|
47
|
+
rules, plus a measured account of where the previous session's window went —
|
|
48
|
+
which file it re-read ten times, which edit kept missing.
|
|
49
|
+
- **The runner now logs what each attempt cost.** One `[context_cost]` line per
|
|
50
|
+
attempt: tool calls, tool output in kB, files read whole, ranged reads, failed
|
|
51
|
+
edits. Diagnosing the run that prompted all of the above meant grepping 1.3 MB
|
|
52
|
+
of stream by hand.
|
|
53
|
+
- **Hosts pinned to a non-Claude model get their dashboard todo list back.** On
|
|
54
|
+
third-party models behind a local proxy the child never called `TodoWrite`, so
|
|
55
|
+
the card rendered empty; the instruction is now explicit for those hosts and
|
|
56
|
+
stays out of the way for Claude's own models, which do it natively.
|
|
57
|
+
|
|
8
58
|
## 0.3.4
|
|
9
59
|
|
|
10
60
|
The install stops taking things away from the host it is setting up. All three
|
|
@@ -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.6"
|
|
14
14
|
end
|
data/libexec/mcptask_runner
CHANGED
|
Binary file
|