From fbab5bb42bf462f473cd191607dccdc23fc09e0e Mon Sep 17 00:00:00 2001 From: nesquena-hermes Date: Sun, 21 Jun 2026 05:32:53 +0000 Subject: [PATCH] =?UTF-8?q?docs(release):=20stamp=20v0.51.549=20=E2=80=94?= =?UTF-8?q?=20hotfix=20profile=20switching=20for=20single-user=20named=20p?= =?UTF-8?q?rofiles=20(#4589/#4586)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 33fee753..f106bcbb 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,12 @@ ## [Unreleased] +## [v0.51.549] — 2026-06-21 — Release TH (hotfix: profile switching restored for single-user named profiles) + +### Fixed + +- **Profile switching works again for normal single-user named profiles (hotfix #4586).** A regression (since v0.51.528) wrongly treated any single user running under a named profile as an isolated multi-user deployment — because isolated mode was inferred from the `HERMES_HOME` path shape (`*/profiles/`), which the agent launcher exports for any named profile. The Profiles tab showed only one profile and switching was disabled. Isolated single-profile mode now requires an explicit `HERMES_WEBUI_ISOLATED_PROFILE` opt-in and is never inferred from the path shape. The opt-in is also protected from being overridden by a profile's own `.env` (on both the live-env and runtime/background-worker paths), so a pinned profile can't disable its own isolation. Thanks @nesquena-hermes. + ## [v0.51.548] — 2026-06-21 — Release TG (extension load diagnostics) ### Added