From b772ccb8dbca148d438555565307efb1e396efda Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 17 Nov 2026 07:27:58 +0000 Subject: [PATCH] chore: version packages --- .changeset/bright-telemetry-shines.md | 5 ----- .changeset/control-stop-restart-hostkey.md | 5 ----- .changeset/deploy-papercuts.md | 5 ----- .changeset/docs-snippet-values.md | 5 ----- .changeset/doctor-host-checks.md | 5 ----- .changeset/green-foxes-check.md | 5 ----- .changeset/ingress-logs-and-tls.md | 5 ----- .changeset/ingress-nodes.md | 5 ----- .changeset/local-qemu-evidence.md | 5 ----- .changeset/quiet-cats-retire.md | 5 ----- .changeset/real-host-docs-vultr.md | 5 ----- .changeset/real-host-main-verification.md | 5 ----- .changeset/test-suite-performance.md | 5 ----- .changeset/vast-steaks-spend.md | 5 ----- CHANGELOG.md | 22 ++++++++++++++++++++++ package-lock.json | 4 ++-- package.json | 2 +- 17 files changed, 25 insertions(+), 73 deletions(-) delete mode 100644 .changeset/bright-telemetry-shines.md delete mode 100644 .changeset/control-stop-restart-hostkey.md delete mode 100644 .changeset/deploy-papercuts.md delete mode 100644 .changeset/docs-snippet-values.md delete mode 100644 .changeset/doctor-host-checks.md delete mode 100644 .changeset/green-foxes-check.md delete mode 100644 .changeset/ingress-logs-and-tls.md delete mode 100644 .changeset/ingress-nodes.md delete mode 100644 .changeset/local-qemu-evidence.md delete mode 100644 .changeset/quiet-cats-retire.md delete mode 100644 .changeset/real-host-docs-vultr.md delete mode 100644 .changeset/real-host-main-verification.md delete mode 100644 .changeset/test-suite-performance.md delete mode 100644 .changeset/vast-steaks-spend.md diff --git a/.changeset/bright-telemetry-shines.md b/.changeset/bright-telemetry-shines.md deleted file mode 100644 index d9d9ed2..0000000 --- a/.changeset/bright-telemetry-shines.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': minor ---- - -Add authenticated control readiness and project-scoped Prometheus metrics, configurable bounded writer admission with retry hints, and structured control/agent logs with safe default failure classifications and opt-in sanitized debug causes. diff --git a/.changeset/control-stop-restart-hostkey.md b/.changeset/control-stop-restart-hostkey.md deleted file mode 100644 index 76e320d..0000000 --- a/.changeset/control-stop-restart-hostkey.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": minor ---- - -Add `tug control stop` and `tug control restart`, which stop or restart the control container over SSH without touching its volume, image or published ports, and make `tug control restore` name `tug control restart` as the next step. Every command that runs SSH now explains `Host key verification failed` and prints the `ssh-keygen -R ` remedy instead of reporting a connection failure, and never edits `known_hosts`. diff --git a/.changeset/deploy-papercuts.md b/.changeset/deploy-papercuts.md deleted file mode 100644 index 13fa419..0000000 --- a/.changeset/deploy-papercuts.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": minor ---- - -Catch deploy problems earlier and report them more clearly. Control refuses a deploy before the build when another project's current deployment publishes the same host port on the same node address, naming the project, node, address and port, and `tug deploy --dry-run` runs the same check through a new route, `POST /api/v1/deployments/check` (a newer CLI against an older control reports the missing route). A missing value that sits in an `x-tug.backup` field now says it may be a container variable that needs `$$` and shows the corrected line. A failed http health check names the full URL the agent requested, with the container address, path and query, and the last status or connection error. The deploy summary and `tug status` show the deployment id when two deployments carry the same version label, which the default `git-` label does for a changed build context, secret or variable. diff --git a/.changeset/docs-snippet-values.md b/.changeset/docs-snippet-values.md deleted file mode 100644 index bc7f71e..0000000 --- a/.changeset/docs-snippet-values.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": patch ---- - -Fix the MariaDB restore example in the Compose reference, which failed `tug deploy` because of an unescaped `$`, and add a test that checks every Compose snippet in the README and docs against the deploy value rules. Add scripts under `tools/scripts` to measure ingress overhead, container CPU and memory, and downtime during a redeploy. diff --git a/.changeset/doctor-host-checks.md b/.changeset/doctor-host-checks.md deleted file mode 100644 index 6b76355..0000000 --- a/.changeset/doctor-host-checks.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': minor ---- - -`tug doctor` now checks that ingress nodes answer on ports 80 and 443 (control opens a TCP connection to each node's address) and fails with the closed port, the likely firewall cause and the fix; tug still never changes a firewall. It prints the local Docker daemon as `skip` with `needed only for --build-local` instead of `FAIL` when none is reachable, and no longer counts it as a problem. Node and control diagnostics report load average, available memory, free disk under Docker's data root and the CPU and memory of the agent, Caddy and control containers. `tug node ingress` reminds the operator to open the ports. Additive: the new checks and fields appear in `doctor --json`, and an agent that predates the resources check simply omits it. diff --git a/.changeset/green-foxes-check.md b/.changeset/green-foxes-check.md deleted file mode 100644 index 1baed6f..0000000 --- a/.changeset/green-foxes-check.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': minor ---- - -Add signed best-effort webhook notifications with bounded retries, startup grace and delivery metrics. Optional notification configuration errors keep control available. Add an external HTTP probe with bounded same-host redirects. diff --git a/.changeset/ingress-logs-and-tls.md b/.changeset/ingress-logs-and-tls.md deleted file mode 100644 index cd4a877..0000000 --- a/.changeset/ingress-logs-and-tls.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': minor ---- - -Add `tug ingress logs [node]` (and the `tug logs --ingress` shorthand) to read an ingress node's Caddy container, and `tug ingress tls [node]` to show per host whether the edge serves a valid certificate and why not. Ingress agents now probe their own Caddy with a TLS handshake per named host and report `issued`, `pending` or `failed` in the ingress status. The state also appears in `tug domain list`, as a count in `tug status`, and in `tug doctor`, which now fails the `ingress` check for a host without a certificate for more than ten minutes. Both commands need an unscoped `admin` credential. The status field is additive, and an agent that predates it reads `unknown`. diff --git a/.changeset/ingress-nodes.md b/.changeset/ingress-nodes.md deleted file mode 100644 index 47e2334..0000000 --- a/.changeset/ingress-nodes.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": minor ---- - -Add `x-tug.ingress.nodes`, the ingress nodes that serve a route. Without it every ingress node serves every route and requests a certificate for every host, so a host that resolves to one node showed as failed on the others. Named routes render only on those nodes, and a deployment waits only for them. diff --git a/.changeset/local-qemu-evidence.md b/.changeset/local-qemu-evidence.md deleted file mode 100644 index dac519a..0000000 --- a/.changeset/local-qemu-evidence.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": patch ---- - -Record local QEMU enrollment and recovery checks, including content verification and remaining coverage limits. diff --git a/.changeset/quiet-cats-retire.md b/.changeset/quiet-cats-retire.md deleted file mode 100644 index 11c796a..0000000 --- a/.changeset/quiet-cats-retire.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': patch ---- - -Document operational reliability and recovery responsibilities, and cover interrupted activation, ENOSPC, damaged-repository recovery, rollout behavior and integration convergence with regression tests. diff --git a/.changeset/real-host-docs-vultr.md b/.changeset/real-host-docs-vultr.md deleted file mode 100644 index a814b66..0000000 --- a/.changeset/real-host-docs-vultr.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": patch ---- - -Fix the MariaDB and PostgreSQL restore recipes in the backup docs, which failed `tug deploy` because of an unescaped `$`. Document host firewalls and the Let's Encrypt retry delay for ingress, the control restart after a restore, and add the 3.0.0 real-host results. diff --git a/.changeset/real-host-main-verification.md b/.changeset/real-host-main-verification.md deleted file mode 100644 index eb0d536..0000000 --- a/.changeset/real-host-main-verification.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@wpelevator/tug": patch ---- - -Add the real-host results for the merged papercut fixes to the evaluation: port probe, ingress certificate state, control stop and restart, host key hint, duplicate port refusal, cross-node names and reboot survival. diff --git a/.changeset/test-suite-performance.md b/.changeset/test-suite-performance.md deleted file mode 100644 index 587d7b3..0000000 --- a/.changeset/test-suite-performance.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': patch ---- - -Start faster: the CLI loads only the command it runs. The CLI now takes its environment, working directory, streams and signals from one runtime object instead of the process, which lets the test suite run commands in-process and finish in less than half the time. diff --git a/.changeset/vast-steaks-spend.md b/.changeset/vast-steaks-spend.md deleted file mode 100644 index fbd38ac..0000000 --- a/.changeset/vast-steaks-spend.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@wpelevator/tug': patch ---- - -Clarify that managed HTTP ingress already balances requests with round robin, distinguish cross-node service-name recovery from seamless failover, and separate future internal balancing from existing ingress in the roadmap. diff --git a/CHANGELOG.md b/CHANGELOG.md index 160749d..86411b5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,27 @@ # @wpelevator/tug +## 3.1.0 + +### Minor Changes + +- d4b995d: Add authenticated control readiness and project-scoped Prometheus metrics, configurable bounded writer admission with retry hints, and structured control/agent logs with safe default failure classifications and opt-in sanitized debug causes. +- ca456aa: Add `tug control stop` and `tug control restart`, which stop or restart the control container over SSH without touching its volume, image or published ports, and make `tug control restore` name `tug control restart` as the next step. Every command that runs SSH now explains `Host key verification failed` and prints the `ssh-keygen -R ` remedy instead of reporting a connection failure, and never edits `known_hosts`. +- ca456aa: Catch deploy problems earlier and report them more clearly. Control refuses a deploy before the build when another project's current deployment publishes the same host port on the same node address, naming the project, node, address and port, and `tug deploy --dry-run` runs the same check through a new route, `POST /api/v1/deployments/check` (a newer CLI against an older control reports the missing route). A missing value that sits in an `x-tug.backup` field now says it may be a container variable that needs `$$` and shows the corrected line. A failed http health check names the full URL the agent requested, with the container address, path and query, and the last status or connection error. The deploy summary and `tug status` show the deployment id when two deployments carry the same version label, which the default `git-` label does for a changed build context, secret or variable. +- ca456aa: `tug doctor` now checks that ingress nodes answer on ports 80 and 443 (control opens a TCP connection to each node's address) and fails with the closed port, the likely firewall cause and the fix; tug still never changes a firewall. It prints the local Docker daemon as `skip` with `needed only for --build-local` instead of `FAIL` when none is reachable, and no longer counts it as a problem. Node and control diagnostics report load average, available memory, free disk under Docker's data root and the CPU and memory of the agent, Caddy and control containers. `tug node ingress` reminds the operator to open the ports. Additive: the new checks and fields appear in `doctor --json`, and an agent that predates the resources check simply omits it. +- d4b995d: Add signed best-effort webhook notifications with bounded retries, startup grace and delivery metrics. Optional notification configuration errors keep control available. Add an external HTTP probe with bounded same-host redirects. +- 3fc8375: Add `tug ingress logs [node]` (and the `tug logs --ingress` shorthand) to read an ingress node's Caddy container, and `tug ingress tls [node]` to show per host whether the edge serves a valid certificate and why not. Ingress agents now probe their own Caddy with a TLS handshake per named host and report `issued`, `pending` or `failed` in the ingress status. The state also appears in `tug domain list`, as a count in `tug status`, and in `tug doctor`, which now fails the `ingress` check for a host without a certificate for more than ten minutes. Both commands need an unscoped `admin` credential. The status field is additive, and an agent that predates it reads `unknown`. +- 75d8a35: Add `x-tug.ingress.nodes`, the ingress nodes that serve a route. Without it every ingress node serves every route and requests a certificate for every host, so a host that resolves to one node showed as failed on the others. Named routes render only on those nodes, and a deployment waits only for them. + +### Patch Changes + +- ca456aa: Fix the MariaDB restore example in the Compose reference, which failed `tug deploy` because of an unescaped `$`, and add a test that checks every Compose snippet in the README and docs against the deploy value rules. Add scripts under `tools/scripts` to measure ingress overhead, container CPU and memory, and downtime during a redeploy. +- f89e0cb: Record local QEMU enrollment and recovery checks, including content verification and remaining coverage limits. +- d4b995d: Document operational reliability and recovery responsibilities, and cover interrupted activation, ENOSPC, damaged-repository recovery, rollout behavior and integration convergence with regression tests. +- 7bb7841: Fix the MariaDB and PostgreSQL restore recipes in the backup docs, which failed `tug deploy` because of an unescaped `$`. Document host firewalls and the Let's Encrypt retry delay for ingress, the control restart after a restore, and add the 3.0.0 real-host results. +- 75d8a35: Add the real-host results for the merged papercut fixes to the evaluation: port probe, ingress certificate state, control stop and restart, host key hint, duplicate port refusal, cross-node names and reboot survival. +- 06e68cc: Start faster: the CLI loads only the command it runs. The CLI now takes its environment, working directory, streams and signals from one runtime object instead of the process, which lets the test suite run commands in-process and finish in less than half the time. +- faf4a3f: Clarify that managed HTTP ingress already balances requests with round robin, distinguish cross-node service-name recovery from seamless failover, and separate future internal balancing from existing ingress in the roadmap. + ## 3.0.0 ### Major Changes diff --git a/package-lock.json b/package-lock.json index 2252bbe..ffd160e 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@wpelevator/tug", - "version": "3.0.0", + "version": "3.1.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@wpelevator/tug", - "version": "3.0.0", + "version": "3.1.0", "license": "MIT", "dependencies": { "@peculiar/x509": "^3.1.0", diff --git a/package.json b/package.json index 154cd12..3ceb5bb 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@wpelevator/tug", - "version": "3.0.0", + "version": "3.1.0", "description": "Portable VPS deployments with Docker Compose", "license": "MIT", "author": "WP Elevator (https://wpelevator.com)",