mcptask-rails-runner 0.3.34-aarch64-linux → 0.3.36-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: 3e4666f2e73047649b6fc947adb3fe81a2579686058bd239dca67dbbd940f028
4
- data.tar.gz: c87a7bdeebe3c41d6041754b9d2c9fc938688801eff609a14fa4a02bd5eaa3f1
3
+ metadata.gz: b38b5313830fa72e114c29b6e1cc197d890667621c3d78c193e4bf3a174ed5d9
4
+ data.tar.gz: 6383fb6a888c8f7af22868ea7974ecf18c638c33e056fa48ea7b9769ad01653e
5
5
  SHA512:
6
- metadata.gz: 325a9481b7d0429270c0f6477438ef71da85fb29d5280c04660e657253bcfa70774a7b52e2e719df6c364831d848111b51805f29aff4d1f678b43924ba4a1dd0
7
- data.tar.gz: 920a4cac12b675118842b38859b1848bb4b18187dbaf181359d787c70e826cd1a37bc0a71de67c427aa58c57cd308feacd4ac943b16f602fb37be8613888d94b
6
+ metadata.gz: 2ad4fbde4181438aa49aa90ce03e3494fe6dc25b8812e5feeca176b2ccaeeccacddf844683f494387f890943bc2d5cf660e8b450c7cffa0c2e85963bf33cadd0
7
+ data.tar.gz: 95a355405bddad6812c6ef216493dafec5c97036b039936409513465106931a7dded38d5a17e6d6e7f32a43b13bf5bdb3395e85bdb2109b3cdd466c2fb1ccf7e
data/CHANGELOG.md CHANGED
@@ -9,6 +9,34 @@ release notes for the same tag.
9
9
 
10
10
  Nothing yet.
11
11
 
12
+ ## 0.3.36
13
+
14
+ Full binary notes in
15
+ [mcptask-releases v0.3.36](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.36).
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 feature catalog the website renders ([Task #13451](https://mcptask.online/jchsoft/tasks/13451))
24
+ - Every release carries `catalog.yml` as an asset ([#13454](https://mcptask.online/jchsoft/tasks/13454))
25
+ - The catalog and the code may not disagree ([Task #13453](https://mcptask.online/jchsoft/tasks/13453))
26
+
27
+ ## 0.3.35
28
+
29
+ Full binary notes in
30
+ [mcptask-releases v0.3.35](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.35).
31
+
32
+ **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.
33
+
34
+ No wrapper changes.
35
+
36
+ Binary changes carried by this version:
37
+
38
+ - Story branches: a Story reaches main in one merge (opt-in) ([Story #13009](https://mcptask.online/jchsoft/stories/13009))
39
+
12
40
  ## 0.3.34
13
41
 
14
42
  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.34"
13
+ VERSION = "0.3.36"
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.34
4
+ version: 0.3.36
5
5
  platform: aarch64-linux
6
6
  authors:
7
7
  - Josef Chmel