mcptask-rails-runner 0.3.1 → 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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: '0519b4bebbc7206e258a1c0ca68d4b33a1d4ca65e7b1df96e94bc7fcea9d195a'
4
- data.tar.gz: fb10b8db54c85034117828907847bb13c62d80f316591490724c2e8804fcebdd
3
+ metadata.gz: b096e58f6c3e2f26793191afd3b4fe43f6b030228e822c1c2826e1ccf6aeb616
4
+ data.tar.gz: 532f1392d6a756c206a65f99497bc0902a7c41cbdb2b7a2277bcb6ca3defef94
5
5
  SHA512:
6
- metadata.gz: 5d80a74fce1cb46bcef44e67e6d17c3015a9651a53fc8099b05fd75abb29c9f5b7f37e22d194f1192cfb6e1a7527ae9c5f3ae21b7462ce5bf43d01c64d49722e
7
- data.tar.gz: 5fa67df8de13a98d9f42990dacfadea7b56b7cb040bbde6186cb9cb1d764ca46f9a191dbb163c4aade6bb4d036334249820af81e389801c7ba95e3279a2c9773
6
+ metadata.gz: c6e1e6b25f742d18938cacae6182cf39ee06f4a473be880db7e806bfa8e94642cd9019dca084054ab064f99fc9ae35831006399619a4dc7c148b3dca6fdd0327
7
+ data.tar.gz: 14d2e35952bcb21ed9118d7fca22ccdb1e2d760f8a2cfecd4a03873046c2951dbd4f595d18b45b7e14ab41bdecf5fff69de234449280de493b8c1a8a2ae8fe22
data/CHANGELOG.md CHANGED
@@ -5,6 +5,23 @@ 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
+
8
25
  ## 0.3.1
9
26
 
10
27
  - `mcptask_runner:install` no longer asks for mcptask.online credentials on a
@@ -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.1"
13
+ VERSION = "0.3.2"
14
14
  end
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.1
4
+ version: 0.3.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Josef Chmel