diff --git a/CHANGELOG.md b/CHANGELOG.md index 636bbbd..cf00f9d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,19 @@ and this project uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html) ## [Unreleased] +## [0.87.0] - 2026-11-02 + +Needs DirXMLDev 0.64.0. + +### Added + +- **Trace size limits in deploys** (DirXMLDev 0.64.0). The tree now records each driver's trace size + limit, and a new driver is created with it and with the trace level and file the tree saw. On the + Deploy step, **write the tree's trace size limits over the vault's** also writes the limit on existing + drivers. Without it the vault keeps its own and the plan notes the difference. It never restarts a + driver, and a limit difference never stops a production deploy as drift. The agent tools `plan_deploy` + and `deploy` take `traceSizeLimit`. + ## [0.86.0] - 2026-11-02 Needs DirXMLDev 0.63.0. diff --git a/docs/agents.md b/docs/agents.md index 64d031c..fa3fb4f 100644 --- a/docs/agents.md +++ b/docs/agents.md @@ -136,7 +136,7 @@ refused instead of overwriting someone else's change. Example arguments: | `environments` | | the project's environments, their tier (dev, test, prd), whether you are connected | | `compare` | **`env`**; `drivers`: a list of the tree's driver names (all when omitted) | the tree against the vault: what a deploy would write | | `compare_environments` | **`env`**, **`with`** | two vaults side by side: what only one holds, values that differ, likely renames, likely causes | -| `plan_deploy` | **`env`**; `drivers`; `restart`: `true` (default) restarts drivers a change needs restarted; `secrets`: `none` (default), `missing` or `all` | a deploy step by step, and what stands in its way | +| `plan_deploy` | **`env`**; `drivers`; `restart`: `true` (default) restarts drivers a change needs restarted; `secrets`: `none` (default), `missing` or `all`; `traceSizeLimit`: `true` writes the tree's trace size limit over an existing driver's (default `false`: the vault keeps its own) | a deploy step by step, and what stands in its way | | `driver_status` | **`env`**; `driver` | the drivers' state, or one driver's | | `trace` | **`env`**, **`driver`** | a driver's recent trace | | `snapshots` | **`env`** | the snapshots earlier deploys took (what a rollback puts back) | @@ -147,7 +147,7 @@ you in the chat**. The agent must not fill it in itself. | Tool | Arguments | What it does | |---|---|---| -| `deploy` | **`env`**, **`confirm`**; `drivers`, `restart`, `secrets` as for `plan_deploy` | deploys, after a snapshot | +| `deploy` | **`env`**, **`confirm`**; `drivers`, `restart`, `secrets`, `traceSizeLimit` as for `plan_deploy` | deploys, after a snapshot | | `rollback` | **`env`**, **`snapshot`** (as `snapshots` lists it), **`confirm`** | puts a snapshot back | | `driver_lifecycle` | **`env`**, **`driver`**, **`action`**: `start`, `stop` or `restart`; **`confirm`** | starts, stops or restarts a driver | diff --git a/docs/features.md b/docs/features.md index 2e4938a..91c6a34 100644 --- a/docs/features.md +++ b/docs/features.md @@ -167,8 +167,10 @@ Every view of the page, by area, in every install; the items marked *local and s - *Deploy*: the plan step by step with nothing written, then the deploy itself (snapshot, write, restart, verify) once you type the environment's name; the secrets mode (leave alone, set the named passwords the vault lacks, re-set every provided secret), *allow missing - secrets* for a first deploy, and *delete from the vault* for a driver the comparison reports - as only there (stopped first; the snapshot keeps it). Against production the plan runs the + secrets* for a first deploy, *write the tree's trace size limits over the vault's* (a new driver + always gets the tree's limit, trace level and file; an existing driver keeps the vault's limit + unless this is ticked, and the plan notes a difference either way), and *delete from the vault* + for a driver the comparison reports as only there (stopped first; the snapshot keeps it). Against production the plan runs the production checks too, before anything is typed, and says what stands in the way in plain words with a button for the way on: *Push*, *Get latest main*, or *Capture 's current state* when its state isn't on record or has changed outside the tree. A capture reads diff --git a/pom.xml b/pom.xml index 49e7042..b0ef0f8 100644 --- a/pom.xml +++ b/pom.xml @@ -6,7 +6,7 @@ com.pointblue.dirxml dirxml-dev-web - 0.86.0 + 0.87.0 MIT License @@ -23,7 +23,7 @@ - 0.63.0 + 0.64.0 1.7.0