mcptask-rails-runner 0.3.1 → 0.3.3
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 -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: d8ce34df845fcba0cc60dafd3a533c7bf89f7dc24eddc885e8ce9d4f53058dc3
|
|
4
|
+
data.tar.gz: 0f04addccfa86eaaba0a6e3db9b3a3fed143b0308d730eeb610ef5c5b9e0a720
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 51a94b4dd7259952d56f94acfeae106d7d00b43e873c728876b0637e49ccec596ad8e097dc048ae01288162ba8e1a699ddc2eab1afd138c8ddac0aa7a74adfc2
|
|
7
|
+
data.tar.gz: 69b9113fcf1e5a29240632c2d9799afd00165d80197adfe26faa580cbfa35388a90992422a8ea47be98c7e670e8bc554a2206cce19678802040b4b65c7ffc4b0
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,48 @@ 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.3
|
|
9
|
+
|
|
10
|
+
- The bundled skills now ask for the model the host actually has. Eight of them
|
|
11
|
+
— `ci-start`, `ci-wait`, `test-start`, `test-wait`, `wait-unlock`, `discover`,
|
|
12
|
+
`memory-search`, `mcptask-read` — ship declaring `model: haiku`, and on a
|
|
13
|
+
project whose `models:` are pinned away from Anthropic that alias is not
|
|
14
|
+
redirected by `ANTHROPIC_DEFAULT_HAIKU_MODEL`: the coding CLI resolves a
|
|
15
|
+
skill's own `model:` against its built-in table, asks for
|
|
16
|
+
`claude-haiku-4-5-20251001`, and gets a 404. The skill then hands the error
|
|
17
|
+
text back **as its result**, which the agent above reads as the skill's answer
|
|
18
|
+
and works on regardless. One host had been running that way for as long as its
|
|
19
|
+
models had been pinned — no CI started, no tests run, nothing discovered — with
|
|
20
|
+
every run reporting success. `install` and `update` now rewrite that line to
|
|
21
|
+
the pinned `primitive`, and say which model the forks will use.
|
|
22
|
+
- The scheduled job's time is asked for instead of being 08:00 and unspoken.
|
|
23
|
+
`--at HH:MM` or `MCPTASK_RUN_AT` answers it without a terminal; a value that is
|
|
24
|
+
not a time of day is refused rather than rounded down to the default. The time
|
|
25
|
+
is printed either way — it used to live in the generated file and nowhere else.
|
|
26
|
+
- The install says how to run the job once by hand, so the first evidence that a
|
|
27
|
+
host works does not have to arrive the next weekday morning.
|
|
28
|
+
- On macOS a re-install boots the old job out by service target
|
|
29
|
+
(`gui/$(id -u)/<label>`) rather than by plist path. The path form answers
|
|
30
|
+
`Boot-out failed: 5: Input/output error` where the target form answers
|
|
31
|
+
`3: No such process`, and only one of those can be acted on.
|
|
32
|
+
|
|
33
|
+
## 0.3.2
|
|
34
|
+
|
|
35
|
+
- A token `mcptask_runner:install` provisions now reaches the scheduled job it
|
|
36
|
+
generates in the same run. It did not: the token was written to a shell export
|
|
37
|
+
file that only the next login shell reads — and launchd reads none — so the job
|
|
38
|
+
got `SET_MCPTASK_TOKEN_HERE` and refused to start at 08:00, even after
|
|
39
|
+
re-running with `FORCE=1`. That took two installs and a new terminal in
|
|
40
|
+
between, and nothing said so.
|
|
41
|
+
- A job written with a placeholder now says it **will not start**, and names both
|
|
42
|
+
ways to fix it. The old wording read as a note and went unnoticed.
|
|
43
|
+
- Re-installing prints how to *reload* the job rather than how to activate it:
|
|
44
|
+
launchd and systemd hold their own copy of a loaded job, so rewriting the file
|
|
45
|
+
changes nothing — including the token — until it is reloaded.
|
|
46
|
+
- The install says where the run log is and how to follow it, how to stop a run
|
|
47
|
+
that is going on, and how to switch the job off. On Windows the activation
|
|
48
|
+
command gained `/F`, without which a re-install printed a command that fails.
|
|
49
|
+
|
|
8
50
|
## 0.3.1
|
|
9
51
|
|
|
10
52
|
- `mcptask_runner:install` no longer asks for mcptask.online credentials on a
|
|
@@ -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.3"
|
|
14
14
|
end
|