pwragent 1.3.9 → 1.3.11

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.
package/README.md CHANGED
@@ -50,6 +50,19 @@ stop the daemon, install the selected version, and start it again. Do not remove
50
50
  the PwrAgent root, Codex home or workspace during updates. There is no automatic
51
51
  CLI updater or automatic systemd enablement.
52
52
 
53
+ `pwragent --version` prints the installed package version. A published package
54
+ also prints its release tag and source commit, for example
55
+ `pwragent 1.3.8 (v1.3.8, commit 0123…)`. `pwragent version` prints the same
56
+ fields as JSON. Neither needs a running daemon.
57
+
58
+ `pwragent status` reports the daemon's version as `running`, read when that
59
+ daemon started, and the package files as `installed`. `restartRequired` is
60
+ `true` when they differ, so the update has not taken effect yet. A daemon
61
+ started before version reporting has no `running` field and also reports
62
+ `true`. Run `status` from the same installation as the daemon, such as the
63
+ `/opt/pwragent` path in the systemd example; another installation compares its
64
+ own files.
65
+
53
66
  ## systemd installation example
54
67
 
55
68
  On a Linux host with systemd, an administrator must first create the dedicated
@@ -91,7 +104,8 @@ sudo -u pwragent env PWRAGENT_HOME=/var/lib/pwragent PWRAGENT_PROFILE=outpost \
91
104
  For a service update, finish or interrupt active work, run
92
105
  `sudo systemctl stop pwragent-headless.service`, repeat the prefix installation
93
106
  with the chosen new version (or `pwragent@latest`), then run
94
- `sudo systemctl start pwragent-headless.service`. Compare the new example unit
107
+ `sudo systemctl start pwragent-headless.service`. Run the `status` command above
108
+ and check that `restartRequired` is `false`. Compare the new example unit
95
109
  with the installed one before deliberately updating it; npm does not overwrite
96
110
  `/etc/systemd/system`. Stopping during a turn can leave its outcome `unknown`.
97
111