mcptask-rails-runner 0.3.5 → 0.3.7
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 +40 -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: d4ee1409bbbcbe22aae073df6ba2425858cfc30d9e74a44e26b8e453335f7d6b
|
|
4
|
+
data.tar.gz: 69b8f65e9a3544fbd90c43d76c355314b4abce819fa663e722bbd687c0a6d620
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 5d2f9ee07e2ef4d11106fc3f626e90ae4c831fd0cac167a495bc7f04a91ddcd054d9b33608b210f14b4f1529409dc657a83caecf61e1ed8b15db4af9931810f5
|
|
7
|
+
data.tar.gz: 043c441b54f4dd71d13c4e8a256c543e6f37a18228df6ce5adb6223212ad5e15ec6c12536c6dd9bf87b79ffce053817a0c1eb9b94659a099c7441e7ed9196411
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,46 @@ 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.7
|
|
9
|
+
|
|
10
|
+
No wrapper changes. Full notes in
|
|
11
|
+
[mcptask-releases v0.3.7](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.7).
|
|
12
|
+
|
|
13
|
+
- **0.3.6 only ever reached one platform — 0.3.7 is that release, delivered.**
|
|
14
|
+
rubygems.org was in the middle of an outage while 0.3.6 was being pushed. The
|
|
15
|
+
six platform gems go up one at a time; `aarch64-linux` landed and the next push
|
|
16
|
+
got a 503, which took the rest of the release down with it. Re-running did not
|
|
17
|
+
help either: rubygems refuses to repush a version that already exists, so the
|
|
18
|
+
job died on the gem it had sent and never reached the five it had not. Every
|
|
19
|
+
platform gets 0.3.7; on `aarch64-linux`, 0.3.6 already carries the same binary.
|
|
20
|
+
|
|
21
|
+
The release job now asks rubygems which gems it already has and skips those, so
|
|
22
|
+
a release interrupted half way can be finished by running it again.
|
|
23
|
+
|
|
24
|
+
## 0.3.6
|
|
25
|
+
|
|
26
|
+
No wrapper changes. Full notes in
|
|
27
|
+
[mcptask-releases v0.3.6](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.6).
|
|
28
|
+
|
|
29
|
+
- **The scheduled job stops running a binary its project has already replaced.**
|
|
30
|
+
`rake mcptask_runner:*` has always installed the gem's bundled binary over
|
|
31
|
+
`~/.mcptask/bin/mcptask_runner` when it was newer; the launchd/systemd job was
|
|
32
|
+
the one path that skipped it, because the generated launcher execs that
|
|
33
|
+
installed copy directly. An unattended host would pull main, run
|
|
34
|
+
`bundle install` while working a task, never call `mcptask_runner:update`, and
|
|
35
|
+
sit on a stale runner indefinitely. A scheduled run now reads the project's own
|
|
36
|
+
`Gemfile.lock`, and if it names a newer wrapper than the running binary, it
|
|
37
|
+
installs that gem's copy and re-runs on it.
|
|
38
|
+
|
|
39
|
+
This is not a download. The runner still never fetches a release on its own —
|
|
40
|
+
it only honours the version already merged and installed on purpose. Set
|
|
41
|
+
`MCPTASK_NO_ADOPT=1` to keep a host's binary pinned regardless.
|
|
42
|
+
|
|
43
|
+
Note the ordering: the already-installed binary is the one that decides whether
|
|
44
|
+
to adopt, so a host starts keeping itself current only once it is running 0.3.6
|
|
45
|
+
or later. Hosts on 0.3.5 and older need one `rake mcptask_runner:update` by hand
|
|
46
|
+
first.
|
|
47
|
+
|
|
8
48
|
## 0.3.5
|
|
9
49
|
|
|
10
50
|
No wrapper changes — this release carries a new binary. 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.7"
|
|
14
14
|
end
|