Repository navigation
chore: version packages - #141
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
November 16, 2026 21:20
86e8d7c to
b1c7c5f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 17, 2026 07:28
b1c7c5f to
b772ccb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@wpelevator/tug@3.1.0
Minor Changes
tug control stopandtug control restart, which stop or restart the control container over SSH without touching its volume, image or published ports, and maketug control restorenametug control restartas the next step. Every command that runs SSH now explainsHost key verification failedand prints thessh-keygen -R <host>remedy instead of reporting a connection failure, and never editsknown_hosts.tug deploy --dry-runruns 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 anx-tug.backupfield 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 andtug statusshow the deployment id when two deployments carry the same version label, which the defaultgit-<Compose hash>label does for a changed build context, secret or variable.tug doctornow 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 asskipwithneeded only for --build-localinstead ofFAILwhen 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 ingressreminds the operator to open the ports. Additive: the new checks and fields appear indoctor --json, and an agent that predates the resources check simply omits it.tug ingress logs [node](and thetug logs --ingressshorthand) to read an ingress node's Caddy container, andtug 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 reportissued,pendingorfailedin the ingress status. The state also appears intug domain list, as a count intug status, and intug doctor, which now fails theingresscheck for a host without a certificate for more than ten minutes. Both commands need an unscopedadmincredential. The status field is additive, and an agent that predates it readsunknown.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
tug deploybecause of an unescaped$, and add a test that checks every Compose snippet in the README and docs against the deploy value rules. Add scripts undertools/scriptsto measure ingress overhead, container CPU and memory, and downtime during a redeploy.tug deploybecause 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.