docs(release): stamp v0.51.549 — hotfix profile switching for single-user named profiles (#4589/#4586)
This commit is contained in:
parent
fba80e6981
commit
fbab5bb42b
1 changed files with 6 additions and 0 deletions
|
|
@ -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/<name>`), 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
|
||||
|
|
|
|||
Loading…
Reference in a new issue