@astrofoundry/pi-astro 0.40.5 → 0.40.6

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@astrofoundry/pi-astro",
3
- "version": "0.40.5",
3
+ "version": "0.40.6",
4
4
  "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
5
5
  "keywords": [
6
6
  "pi-package"
@@ -49,6 +49,8 @@ Apply updates only when asked, one stack at a time, with `["stack-update", "<sta
49
49
  - Checks: every service has a container that runs (a one-shot job may have exited 0), found through its Compose project, none still runs an older image than its tag, none is unhealthy or still starting after 5 minutes, and a fresh check finds every updated image current.
50
50
  - A failed check after a Compose change reverts the commit, pushes, waits for the sync, and redeploys the previous file. A pull alone cannot be undone; say so when it fails.
51
51
 
52
+ `stack-update` only moves a stack to what `update-report` offers. Any other image change to one service (a tag switch such as `pr-plugins` to `nightly`, a pin, a digest) goes through the definitions path above: write the Compose file back with only that `image:` line changed, check `git diff` shows that one line, commit, push, and start the stack's sync. On sync, Compose recreates only the services whose configuration or image changed and keeps their volumes (Docker's `docker compose up` reference), so the rest of the stack keeps running. Before the change, record the running image; afterwards, check the service's container, health, and running version. What the tools cannot check (an app's plugin page, a restore into a volume) goes to the owner as a named step, not as a reason to stop.
53
+
52
54
  The answer is JSON with `status`: `updated`, `rolled back`, `failed` (with `reason`), or `nothing to do`, plus `services` (`service`, `from`, `to`, `applied`: `pull` or the new reference, `result`: `current`, `behind`, `unchecked`) and `commit`/`revert` when the Compose file changed. Report it in plain words.
53
55
 
54
56
  It refuses `arcane` (next section), stopped stacks (a redeploy would start them), a checkout with local or unpushed changes, and held stacks. Held stacks are listed in `update-holds.json` at the root of the GitOps repository, `{ "<stack>": "<reason>" }`; `update-report` returns them in `holds`, and the daily report shows the reason without a button. Change that file only when the caller asks, through the `git` commands.