mcptask-rails-runner 0.3.22 → 0.3.24
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 +69 -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: 0de9cc0b17c611f58b8efd32a409010ee8f1048381dec7dcecf0361f2d7371d6
|
|
4
|
+
data.tar.gz: bd0afa59b95660c261aee8b9f9ac3c53c7c4d7befa64d4728c673273c4ef35e4
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 1044df8aa438ef96b8341fdb7c204d7902aefb204db500d606fdcbeea830362b1f0cce837c08b8e804cca0cf84a06fbb9c60e2871818bc82a51a0e769bedca6f
|
|
7
|
+
data.tar.gz: 88c26468384859230763ab8f228a733e4d4ac9e448dd41bd8f02dfc2f9725d0aefe14d102b3215b36f5d06e5e4e94a372a6adc1ee8b3579227dd3919e961b717
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,75 @@ 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.24
|
|
9
|
+
|
|
10
|
+
No wrapper changes. Full notes in
|
|
11
|
+
[mcptask-releases v0.3.24](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.24).
|
|
12
|
+
|
|
13
|
+
**Upgrading takes two commands this time.** `mcptask_runner update --self`
|
|
14
|
+
replaces the binary; then a bare `mcptask_runner update` in any one project on
|
|
15
|
+
the host, because the helper scripts in `~/.claude/bin` changed and the binary
|
|
16
|
+
does not rewrite them on its own. Until that second step runs, a suite started
|
|
17
|
+
through `/ci-runner` finds the test lock held by the old `ci_start` and refuses
|
|
18
|
+
itself as if another agent held it (task #12369).
|
|
19
|
+
|
|
20
|
+
Binary changes carried by this version:
|
|
21
|
+
|
|
22
|
+
- **`harness:` is required in `config/mcptask_runner.yml`.** The runner drives
|
|
23
|
+
a coding CLI named by a profile — `claude`, `codex` or `opencode` — and there
|
|
24
|
+
is no default. `update` writes `harness: claude` once for a project it
|
|
25
|
+
already installed into and says so; a new project needs
|
|
26
|
+
`mcptask_runner init --cli <name>`; a project with neither refuses to start
|
|
27
|
+
and names the key (stories #12276, #12279).
|
|
28
|
+
- **Codex CLI and OpenCode are supported harnesses.** `init --cli codex` and
|
|
29
|
+
`init --cli opencode` set a project up for those CLIs; the work loop, the
|
|
30
|
+
card and the mcptask.online protocol are unchanged. Codex login is done once
|
|
31
|
+
by hand (`codex login`); the runner checks it before a run. Both harnesses
|
|
32
|
+
were driven for real on 2026-09-09 (stories #12277, #12278).
|
|
33
|
+
- **The runner card shows the harness** beside the model, and `version` opens
|
|
34
|
+
with a `Harness: <name> -> <binary>` line (story #12279).
|
|
35
|
+
- **`bin/ci` takes the machine-wide test lock itself** and refuses out loud when
|
|
36
|
+
somebody else holds it (task #12369).
|
|
37
|
+
- A failed dashboard dial no longer prints the bearer token into the run log
|
|
38
|
+
(task #12379); a scripted `init` with no terminal skips the prompts instead
|
|
39
|
+
of dying at them (task #12382); the boot banner names the model ids of the
|
|
40
|
+
profile actually in use (task #12381).
|
|
41
|
+
|
|
42
|
+
## 0.3.23
|
|
43
|
+
|
|
44
|
+
No wrapper changes. Full notes in
|
|
45
|
+
[mcptask-releases v0.3.23](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.23).
|
|
46
|
+
|
|
47
|
+
**Upgrading is the usual one command** — `mcptask_runner update --self`. The
|
|
48
|
+
skills-and-helpers data pack did not change in this version, so a follow-up
|
|
49
|
+
bare `update` is not required; the changes below live in the binary itself.
|
|
50
|
+
|
|
51
|
+
Binary changes carried by this version:
|
|
52
|
+
|
|
53
|
+
- **`--ignore-quota` now means ignore, everywhere.** The daily mode's
|
|
54
|
+
day-level scheduler used to keep asking mcptask.online about the budget even
|
|
55
|
+
with the flag set, so a REST outage could park an unattended daily host
|
|
56
|
+
until the next business day. With the flag set the runner now performs no
|
|
57
|
+
budget queries at all; the end-of-workday clock still applies — it is a time
|
|
58
|
+
rule, not a quota rule (task #11891).
|
|
59
|
+
- **The work window keeps its minutes.** `mcptask_runner init --until 18:30`
|
|
60
|
+
now stores `work_window.end_of_workday_minute` next to the existing hour key
|
|
61
|
+
and the loop stops picking up new work at 18:30, not 18:00. The key is
|
|
62
|
+
additive: a config without it means `:00`, so existing hosts change nothing.
|
|
63
|
+
A value the config cannot hold is refused loudly, never rounded — `--until`
|
|
64
|
+
used to keep only the hour and say nothing (tasks #11892, #11896).
|
|
65
|
+
- **`update` protects locally modified helper scripts** the way it has always
|
|
66
|
+
protected skills: content hashes in a manifest, one of five outcomes per
|
|
67
|
+
file (added / up-to-date / updated / conflict-skipped / force-updated), and
|
|
68
|
+
a `.bak` next to anything `FORCE=1` overwrites. On the first `update` after
|
|
69
|
+
this release, a helper edited by hand reports `conflict-skipped` instead of
|
|
70
|
+
being silently overwritten — that is the fix working, not a failure
|
|
71
|
+
(task #11894).
|
|
72
|
+
- The Ruby-gem conformance baseline now runs nightly in CI rather than on
|
|
73
|
+
every push, and the docs stopped contradicting each other about its role
|
|
74
|
+
(task #11893). Stale comments aligned (task #11895) and a Windows-only
|
|
75
|
+
test flake pinned down (task #11897).
|
|
76
|
+
|
|
8
77
|
## 0.3.22
|
|
9
78
|
|
|
10
79
|
No wrapper changes. Full notes in
|
|
@@ -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.24"
|
|
14
14
|
end
|