mcptask-rails-runner 0.3.0 → 0.3.2
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 +29 -0
- data/README.md +17 -5
- 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: b096e58f6c3e2f26793191afd3b4fe43f6b030228e822c1c2826e1ccf6aeb616
|
|
4
|
+
data.tar.gz: 532f1392d6a756c206a65f99497bc0902a7c41cbdb2b7a2277bcb6ca3defef94
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: c6e1e6b25f742d18938cacae6182cf39ee06f4a473be880db7e806bfa8e94642cd9019dca084054ab064f99fc9ae35831006399619a4dc7c148b3dca6fdd0327
|
|
7
|
+
data.tar.gz: 14d2e35952bcb21ed9118d7fca22ccdb1e2d760f8a2cfecd4a03873046c2951dbd4f595d18b45b7e14ab41bdecf5fff69de234449280de493b8c1a8a2ae8fe22
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,35 @@ 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.2
|
|
9
|
+
|
|
10
|
+
- A token `mcptask_runner:install` provisions now reaches the scheduled job it
|
|
11
|
+
generates in the same run. It did not: the token was written to a shell export
|
|
12
|
+
file that only the next login shell reads — and launchd reads none — so the job
|
|
13
|
+
got `SET_MCPTASK_TOKEN_HERE` and refused to start at 08:00, even after
|
|
14
|
+
re-running with `FORCE=1`. That took two installs and a new terminal in
|
|
15
|
+
between, and nothing said so.
|
|
16
|
+
- A job written with a placeholder now says it **will not start**, and names both
|
|
17
|
+
ways to fix it. The old wording read as a note and went unnoticed.
|
|
18
|
+
- Re-installing prints how to *reload* the job rather than how to activate it:
|
|
19
|
+
launchd and systemd hold their own copy of a loaded job, so rewriting the file
|
|
20
|
+
changes nothing — including the token — until it is reloaded.
|
|
21
|
+
- The install says where the run log is and how to follow it, how to stop a run
|
|
22
|
+
that is going on, and how to switch the job off. On Windows the activation
|
|
23
|
+
command gained `/F`, without which a re-install printed a command that fails.
|
|
24
|
+
|
|
25
|
+
## 0.3.1
|
|
26
|
+
|
|
27
|
+
- `mcptask_runner:install` no longer asks for mcptask.online credentials on a
|
|
28
|
+
host whose token already resolves — from `.mcp.json` or the environment. It
|
|
29
|
+
says which one it found and where, and leaves it alone; set `MCPTASK_EMAIL`
|
|
30
|
+
and `MCPTASK_PASSWORD` to replace it deliberately. Where there really is no
|
|
31
|
+
token, the step now says whose account it wants, that the password is
|
|
32
|
+
exchanged once and never stored, which file the token lands in, and that the
|
|
33
|
+
runner will not start without one.
|
|
34
|
+
- The release workflow waits for the Go binaries instead of failing when the two
|
|
35
|
+
tags are pushed minutes apart.
|
|
36
|
+
|
|
8
37
|
## 0.3.0
|
|
9
38
|
|
|
10
39
|
- The Go runner is the runner: this gem is the Rails distribution, and the
|
data/README.md
CHANGED
|
@@ -118,11 +118,23 @@ bundle exec rake package:all # build all platform gems into pkg/
|
|
|
118
118
|
|
|
119
119
|
## Releasing
|
|
120
120
|
|
|
121
|
-
Releases are cut by tagging
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
121
|
+
Releases are cut by tagging, twice — the binaries come from the Go repository
|
|
122
|
+
and the gems from this one:
|
|
123
|
+
|
|
124
|
+
```bash
|
|
125
|
+
# 1. bump lib/mcptask_rails_runner/version.rb, commit, push
|
|
126
|
+
# 2. in mcptask_go_runner:
|
|
127
|
+
git tag -a v0.3.0 -m v0.3.0 && git push origin v0.3.0
|
|
128
|
+
# 3. here, straight after — no waiting:
|
|
129
|
+
git tag -a v0.3.0 -m v0.3.0 && git push origin v0.3.0
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
Step 3 needs no waiting because the Release workflow's fetch waits for the
|
|
133
|
+
binaries itself (`MCPTASK_WAIT_FOR_RELEASE`, 15 minutes against a Go release
|
|
134
|
+
that takes about four). It then verifies each archive against the release's
|
|
135
|
+
`checksums.txt`, builds the platform gems and publishes them to rubygems.org
|
|
136
|
+
through OIDC trusted publishing. A tag that disagrees with `version.rb` is
|
|
137
|
+
refused before anything is downloaded. See `.github/workflows/release.yml`.
|
|
126
138
|
|
|
127
139
|
One-time setup on rubygems.org, before the first tag can publish anything —
|
|
128
140
|
the gem name has to exist as a trusted-publisher entry:
|
|
@@ -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.2"
|
|
14
14
|
end
|