mcptask-rails-runner 0.3.25-aarch64-linux → 0.3.26-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 +31 -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: 8ecb45f8a09974edf1f48a0eaa5d9612937a92e60dd7542e4580f6f5b5a41e9c
|
|
4
|
+
data.tar.gz: 0b0ef7f3c21b10ee4427fafc32bb2239b0c2e7482b5463f684a36da3144c1791
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 3c20434e7c5a8aa8df8525ea31ea40829c9e0699928b37d23a984c272d650682580f7955712d19a287dba38abc20f565ae98a2958039598ff55e0919be7af49f
|
|
7
|
+
data.tar.gz: 3f952c903dac4f8ca0d84158beabd645d0647c59409221cd96ca67f326139f0b4081b7b0225b26e05c9ec27843306a017ff83d9438ffa8a58aaaba95ef17326f
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,37 @@ 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.26
|
|
9
|
+
|
|
10
|
+
No wrapper changes. Full notes in
|
|
11
|
+
[mcptask-releases v0.3.26](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.26).
|
|
12
|
+
|
|
13
|
+
**Upgrading takes two commands again.** `mcptask_runner update --self`
|
|
14
|
+
replaces the binary; then a bare `mcptask_runner update` in any one project on
|
|
15
|
+
the host, because the bundled `pr` skill gained the review commands. Run it
|
|
16
|
+
while no runner is working that checkout.
|
|
17
|
+
|
|
18
|
+
Binary changes carried by this version:
|
|
19
|
+
|
|
20
|
+
- **Auto-squash asks the git host whether its checks passed before merging.**
|
|
21
|
+
`mcptask_runner pr checks <n>` sits between the local `bin/ci` gate and the
|
|
22
|
+
merge: SUCCESS or NONE merge, FAILED ends `ci_failed` with the PR left open,
|
|
23
|
+
IN_PROGRESS waits (bounded). A green local gate is no longer permission to
|
|
24
|
+
merge; `status_detail` in the result marker says which verdict applied
|
|
25
|
+
(task #12425, found on the real Bitbucket verification of #12365).
|
|
26
|
+
- **The review executors speak `mcptask_runner pr` only.** `pr list --open`
|
|
27
|
+
and `pr reviews <n>` (verdicts and inline notes, on GitHub and Bitbucket)
|
|
28
|
+
replaced the last `gh` calls in any prompt the runner composes (task #12420).
|
|
29
|
+
- **`init --home-dir` re-roots the Bitbucket credential** like the mcptask
|
|
30
|
+
token, and a re-run on a Bitbucket project says whether it left the
|
|
31
|
+
credential alone and which variables it wanted (task #12424).
|
|
32
|
+
- **Run records say how the attempt ended.** `final_status` in
|
|
33
|
+
`log/runs/run_*.json` carries the verdict (`success`, `ci_failed`,
|
|
34
|
+
`merge_unverified`, …) instead of repeating `processing` (task #12426).
|
|
35
|
+
- **A close code the server sent is logged even when the write failure is
|
|
36
|
+
noticed first**; the reader's account gets its own line when the reconnect
|
|
37
|
+
notice already went out (task #12421).
|
|
38
|
+
|
|
8
39
|
## 0.3.25
|
|
9
40
|
|
|
10
41
|
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.26"
|
|
14
14
|
end
|
data/libexec/mcptask_runner
CHANGED
|
Binary file
|