mcptask-rails-runner 0.3.6-aarch64-linux → 0.3.8-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 +4 -4
- data/CHANGELOG.md +34 -0
- data/lib/mcptask_rails_runner/version.rb +1 -1
- data/libexec/mcptask_runner +0 -0
- 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: 184af8d04ba86557680dca8a4f5fd21d6aefb1506f4555fa666e08796f0c5eb3
|
|
4
|
+
data.tar.gz: d4969a8ffa316a691b212333c1fce0a0af21adffac2262ca5f11165d9c56bf23
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 0f789449021c5dedf0271bc17cd08b5ba72885ca92fa527b0246980d214e8f2ed3bd2ce6ab36225557145259a76a1987a3031884c3f48303a71c80107c37ca69
|
|
7
|
+
data.tar.gz: 8d26c741bcd3a891ea923bdbc2a4b8b069c6f8b9b3b439ccdbfe584de7b20eed66c5e1a8af4b6e1be889c1b90574247a509353c16c86d7a7d22031ee44c29dca
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,40 @@ 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.8
|
|
9
|
+
|
|
10
|
+
No wrapper changes. Full notes in
|
|
11
|
+
[mcptask-releases v0.3.8](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.8).
|
|
12
|
+
|
|
13
|
+
- **A run that merged its PR no longer reports none of the work it did.** The
|
|
14
|
+
auto-squash prompt stated its progress-logging cadence in a block after the
|
|
15
|
+
last numbered step; an agent working that fourteen-step spine for half an hour
|
|
16
|
+
never came back to it. One task ran 36 minutes, completed every step, merged,
|
|
17
|
+
and logged nothing — the effort only reached the dashboard because a later pass
|
|
18
|
+
re-picked the task. Each milestone is now named at the step where it falls due,
|
|
19
|
+
the CI-failed path gets a logging point it never had, and a resumed session
|
|
20
|
+
keeps the cadence instead of losing it with the rest of the workflow.
|
|
21
|
+
|
|
22
|
+
- **The end of the working day is a setting rather than a constant.** The runner
|
|
23
|
+
stopped at 18:00 no matter what; the installer now asks, and `--until` sets it
|
|
24
|
+
per run.
|
|
25
|
+
|
|
26
|
+
## 0.3.7
|
|
27
|
+
|
|
28
|
+
No wrapper changes. Full notes in
|
|
29
|
+
[mcptask-releases v0.3.7](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.7).
|
|
30
|
+
|
|
31
|
+
- **0.3.6 only ever reached one platform — 0.3.7 is that release, delivered.**
|
|
32
|
+
rubygems.org was in the middle of an outage while 0.3.6 was being pushed. The
|
|
33
|
+
six platform gems go up one at a time; `aarch64-linux` landed and the next push
|
|
34
|
+
got a 503, which took the rest of the release down with it. Re-running did not
|
|
35
|
+
help either: rubygems refuses to repush a version that already exists, so the
|
|
36
|
+
job died on the gem it had sent and never reached the five it had not. Every
|
|
37
|
+
platform gets 0.3.7; on `aarch64-linux`, 0.3.6 already carries the same binary.
|
|
38
|
+
|
|
39
|
+
The release job now asks rubygems which gems it already has and skips those, so
|
|
40
|
+
a release interrupted half way can be finished by running it again.
|
|
41
|
+
|
|
8
42
|
## 0.3.6
|
|
9
43
|
|
|
10
44
|
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.8"
|
|
14
14
|
end
|
data/libexec/mcptask_runner
CHANGED
|
Binary file
|