From d61e661099b4b6a974d919da575f9246f04569fa Mon Sep 17 00:00:00 2001 From: William Mantly Date: Tue, 28 Jul 2026 14:17:21 -0400 Subject: [PATCH] Bump sso-manager-node to v1.7.0, proxy to v1.5.3, jump-host to v1.8.0 Co-Authored-By: Claude Sonnet 5 --- CHANGELOG.md | 20 ++++++++++++++++++++ jump-host | 2 +- proxy | 2 +- sso-manager-node | 2 +- 4 files changed, 23 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8099e5c..cd41560 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,26 @@ for what changed inside the apps it composes. ## [Unreleased] +## [1.13.0] - 2026-07-28 + +### Fixed +Found via feedback on a fresh install: +- **jump-host's OAuth client had no parent in the Directory.** `seedDirectory()` only ever linked the proxy's OAuth client; jump-host's own (minted by `provisionJumpHost`) was created but never passed through, so it never got a `ResourceEdge`. Existing deployments self-heal on the next `setup.sh` run. +- **TUI-mode SSH connections (bare `ssh user@host`) could drop** with "PTY allocation request failed" / "shell request failed" — a session-listener race in jump-host, same class of bug `runGrammar` already had a fix for. +- **Every form submit briefly showed literal HTML** instead of a loading spinner, across all three apps. +- **`POST /api/user/` and `PUT /api/user/password` had no success message** — a green notification with nothing in it right after adding a user. +- **The login page gave no explanation for why the user landed there** when redirected mid-OAuth-flow. + +### Changed +- **Directory: tree view is now the only view; clicking a resource's name opens its detail modal.** + +### Bumped +- sso-manager-node -> [v1.7.0](https://github.com/theta42/sso-manager-node/releases/tag/v1.7.0) +- proxy -> [v1.5.3](https://github.com/theta42/proxy/releases/tag/v1.5.3) +- jump-host -> [v1.8.0](https://github.com/theta42/jump-host/releases/tag/v1.8.0) + +No `setup.sh` or compose change. Also confirmed (no fix needed): the Let's Encrypt ACME account key persists correctly across container rebuilds — `lua-resty-auto-ssl`'s Redis storage adapter writes through the bundled Redis, which is started with `--appendonly yes` into `/data`, mapped to the persisted `proxy-data` volume. Only an explicit `docker-compose down -v` / volume removal would lose it (which is also what's required, and expected, on a domain change). + ## [1.12.0] - 2026-07-28 ### Bumped diff --git a/jump-host b/jump-host index 0af2fc7..21ef896 160000 --- a/jump-host +++ b/jump-host @@ -1 +1 @@ -Subproject commit 0af2fc7e3d8d9cdbd08ab0294a3b624b35d29b2d +Subproject commit 21ef8960c42694419b9028a2deabc39f979b4085 diff --git a/proxy b/proxy index 001fe84..44c2ec3 160000 --- a/proxy +++ b/proxy @@ -1 +1 @@ -Subproject commit 001fe84b99d78aceff0e53f29d8665fe4ded8fe7 +Subproject commit 44c2ec3fddcc4de8d79125f34c0245abc4c1a758 diff --git a/sso-manager-node b/sso-manager-node index 1b0418e..6988383 160000 --- a/sso-manager-node +++ b/sso-manager-node @@ -1 +1 @@ -Subproject commit 1b0418e42e509164a5607c858122fb32de5a9920 +Subproject commit 69883836e1f4c46b246ff26bd5d29fe272db54d7