mcptask-rails-runner 0.3.30-aarch64-linux → 0.3.32-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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 8cc6ea40c77353f78bcb3b25dfcbc2ba88d4a30e41b8f43e106c59fce7aafd48
4
- data.tar.gz: e72159ec9c96761c4dc01adb23da53584b87c58f18b8d30bb47413984d63a39d
3
+ metadata.gz: 8a1baa5a7c3dfc67837a57cbd37211a780b62c655b180913cb3afc046b2fe397
4
+ data.tar.gz: 64f59da7fffcafbd7cdbc100629bebcd4e9361e710f2b3f2afc4e392f01cb118
5
5
  SHA512:
6
- metadata.gz: 7e7668abe314c86adbbf3c8528e8fe47e86b5239ce6cf579a2af0048215bc3284e1848009ca17c54921a2f62b33be23eab19e7edd013a28ad4a60e8bb0f34634
7
- data.tar.gz: 306a5d1273cdb2fd059156b2d5b0dc1eac343ff398115fb316e0a0dca83359906237790566838619a1f44c2f5fe7060daec4ed22cf0902bdfa163d5a6e6ee533
6
+ metadata.gz: bf94945378fc2a333ac6128fc3f454773c4c3e8eea02ff7241ea2d3198def319dea53d191ba18e46674bf3721ad60aa66ad18458b6c6aa92bfc3862efa902373
7
+ data.tar.gz: 1698884ef7b3d0f43b8c6b5a95d75412c98acd1a5e95da4d89609e15678420b1c8717b46be453ccc32fa4f744346d1af24337f14f912c94f988c2f6b5b512e4c
data/CHANGELOG.md CHANGED
@@ -9,6 +9,42 @@ release notes for the same tag.
9
9
 
10
10
  Nothing yet.
11
11
 
12
+ ## 0.3.32
13
+
14
+ Full binary notes in
15
+ [mcptask-releases v0.3.32](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.32).
16
+
17
+ **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.
18
+
19
+ No wrapper changes.
20
+
21
+ Binary changes carried by this version:
22
+
23
+ - A second `bundle update` in one day is taken up too ([#12905](https://mcptask.online/jchsoft/tasks/12905))
24
+ - A refused push ends the task; it is no longer worked around ([#12903](https://mcptask.online/jchsoft/tasks/12903))
25
+ - 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))
26
+ - A fan-out of subagents over one file is no longer killed as a loop ([#12966](https://mcptask.online/jchsoft/tasks/12966))
27
+ - `ollama launch` works again, and a CLI that cannot start says so ([#12965](https://mcptask.online/jchsoft/tasks/12965))
28
+
29
+ ## 0.3.31
30
+
31
+ Full binary notes in
32
+ [mcptask-releases v0.3.31](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.31).
33
+
34
+ **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.
35
+
36
+ No wrapper changes.
37
+
38
+ Binary changes carried by this version:
39
+
40
+ - The installed skills and helpers follow the binary by themselves
41
+ - Run logs and bug-report attachments no longer carry escape codes
42
+ - The release is one script
43
+ - A child that forks subagents in the foreground is no longer killed at five minutes
44
+ - A transient 500 from the API no longer ends the day
45
+ - A running runner takes up a newly installed binary between tasks
46
+ - The story loop asks the server which subtask is next
47
+
12
48
  ## 0.3.30
13
49
 
14
50
  Full binary 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.30"
13
+ VERSION = "0.3.32"
14
14
  end
Binary file
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: mcptask-rails-runner
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.30
4
+ version: 0.3.32
5
5
  platform: aarch64-linux
6
6
  authors:
7
7
  - Josef Chmel