From cf8c5c9a040daa52f6c42997dc9eb54b58300438 Mon Sep 17 00:00:00 2001
From: William Mantly <wmantly@gmail.com>
Date: Tue, 28 Jul 2026 15:58:42 -0400
Subject: [PATCH] Bump jump-host to v1.8.1 (#107)

---
 CHANGELOG.md | 11 +++++++++++
 jump-host    |  2 +-
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index cd41560..8c32282 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,17 @@ for what changed inside the apps it composes.
 
 ## [Unreleased]
 
+## [1.14.0] - 2026-07-28
+
+### Fixed
+- **jump-host's Redis had zero persistence** (`--save '' --appendonly no`, no data-dir volume) — every container rebuild/recreation (including a `setup.sh` re-run) silently wiped all sessions, in-flight OAuth logins, and any admin-created API token. This is the root cause of the reported "re-running setup.sh breaks OAuth with jump" — the jump-host container gets recreated, and any token or in-flight login vanished with it, while proxy was unaffected because its Redis was already persisted. Now jump-host's Redis persists (AOF + periodic RDB) to `/data`, mounted as a new named volume, `jump-redis-data`. Verified live: minted a PAT, force-recreated the container, confirmed the same PAT still authenticated afterward.
+
+### Changed
+- `docker-compose.yml`: added the `jump-redis-data` volume, mounted at `/data` on the `jump-host` service.
+
+### Bumped
+- jump-host -> [v1.8.1](https://github.com/theta42/jump-host/releases/tag/v1.8.1)
+
 ## [1.13.0] - 2026-07-28
 
 ### Fixed
diff --git a/jump-host b/jump-host
index 21ef896..1d09f24 160000
--- a/jump-host
+++ b/jump-host
@@ -1 +1 @@
-Subproject commit 21ef8960c42694419b9028a2deabc39f979b4085
+Subproject commit 1d09f243dd9dfac5d479357dde7085d685db1e66