mcptask-rails-runner 0.3.2 → 0.3.4
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
- 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: 2a59e79a3c1d27d4439e3dacd64b8c571b40ec6b09f4298c17e44bc50333266e
|
|
4
|
+
data.tar.gz: c5ac6c24611c7e971c3920a47e404302754bbc3be05ad4d5eb66efefdf6dc465
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 5c692cb004f386155b6d238c4a98bdfc613f2103d751a9d3ad5ed866ccacb6afffb47f29b3dd5209de6ea0b147a10830ac31774fe918ffca57114fa947312d2e
|
|
7
|
+
data.tar.gz: 84f6b21412e4fe8a44efdeade405aa32b520264acd7fa88290a45b5413932a497db61d05242d8f98d4ea8866668a9f1f0dd14e22ca9a42cc106a2df615fe2776
|
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.4
|
|
9
|
+
|
|
10
|
+
The install stops taking things away from the host it is setting up. All three
|
|
11
|
+
of these were in every release up to and including 0.3.3.
|
|
12
|
+
|
|
13
|
+
- **A project's own token variable survives.** `init` replaced the whole
|
|
14
|
+
`mcptask-online` entry in `.mcp.json` with one hardcoding
|
|
15
|
+
`Bearer ${MCPTASK_TOKEN}` — on every install, not only `--force`. A project
|
|
16
|
+
naming its own variable, and so its own mcptask.online account, was quietly
|
|
17
|
+
moved onto whatever account `MCPTASK_TOKEN` happened to hold. That does not
|
|
18
|
+
fail: it succeeds as the wrong user, and every task, effort and bug lands on
|
|
19
|
+
somebody else's dashboard, with the scheduled job carrying that token to 08:00.
|
|
20
|
+
- **A token living inside `.mcp.json` is no longer deleted.** The legacy gem's
|
|
21
|
+
installer wrote tokens into an `env` block on the entry, which makes it the
|
|
22
|
+
shape a migrating host arrives in. Replacing the entry removed the only copy —
|
|
23
|
+
nothing else had it, because a token that already resolves is deliberately left
|
|
24
|
+
alone — and the job then got `SET_MCPTASK_TOKEN_HERE` with nothing left to
|
|
25
|
+
re-resolve, so re-running could not repair it. Such an entry is now left exactly
|
|
26
|
+
as it is, and the install says so.
|
|
27
|
+
- **An unparseable `.mcp.json` is refused, not replaced.** It used to be treated
|
|
28
|
+
as absent, which deleted every other MCP server configured in it. One trailing
|
|
29
|
+
comma was enough, and a project that already runs a coding CLI with servers of
|
|
30
|
+
its own is the normal case. The install now names the file and the parse error;
|
|
31
|
+
`--force` moves it aside to `.mcp.json.bak` and writes a fresh one.
|
|
32
|
+
|
|
33
|
+
## 0.3.3
|
|
34
|
+
|
|
35
|
+
- The bundled skills now ask for the model the host actually has. Eight of them
|
|
36
|
+
— `ci-start`, `ci-wait`, `test-start`, `test-wait`, `wait-unlock`, `discover`,
|
|
37
|
+
`memory-search`, `mcptask-read` — ship declaring `model: haiku`, and on a
|
|
38
|
+
project whose `models:` are pinned away from Anthropic that alias is not
|
|
39
|
+
redirected by `ANTHROPIC_DEFAULT_HAIKU_MODEL`: the coding CLI resolves a
|
|
40
|
+
skill's own `model:` against its built-in table, asks for
|
|
41
|
+
`claude-haiku-4-5-20251001`, and gets a 404. The skill then hands the error
|
|
42
|
+
text back **as its result**, which the agent above reads as the skill's answer
|
|
43
|
+
and works on regardless. One host had been running that way for as long as its
|
|
44
|
+
models had been pinned — no CI started, no tests run, nothing discovered — with
|
|
45
|
+
every run reporting success. `install` and `update` now rewrite that line to
|
|
46
|
+
the pinned `primitive`, and say which model the forks will use.
|
|
47
|
+
- The scheduled job's time is asked for instead of being 08:00 and unspoken.
|
|
48
|
+
`--at HH:MM` or `MCPTASK_RUN_AT` answers it without a terminal; a value that is
|
|
49
|
+
not a time of day is refused rather than rounded down to the default. The time
|
|
50
|
+
is printed either way — it used to live in the generated file and nowhere else.
|
|
51
|
+
- The install says how to run the job once by hand, so the first evidence that a
|
|
52
|
+
host works does not have to arrive the next weekday morning.
|
|
53
|
+
- On macOS a re-install boots the old job out by service target
|
|
54
|
+
(`gui/$(id -u)/<label>`) rather than by plist path. The path form answers
|
|
55
|
+
`Boot-out failed: 5: Input/output error` where the target form answers
|
|
56
|
+
`3: No such process`, and only one of those can be acted on.
|
|
57
|
+
|
|
8
58
|
## 0.3.2
|
|
9
59
|
|
|
10
60
|
- A token `mcptask_runner:install` provisions now reaches the scheduled job it
|
|
@@ -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.4"
|
|
14
14
|
end
|