docs(changelog): note browser cookie persistence#100507
Merged
Merged
Conversation
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 6, 2026
giodl73-repo
pushed a commit
to giodl73-repo/openclaw
that referenced
this pull request
Jul 8, 2026
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
1 participant
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.
What Problem This Solves
The maintained Browser cookie-persistence fix landed in #98284 without a contributor-owned changelog edit. The Unreleased changelog needs to describe the user-visible behavior and credit the contributor.
Why This Change Was Made
Keep release-owned changelog work on a maintainer branch while recording both parts of the bounded fix: stable encryption for new isolated macOS headless profiles and graceful Chromium shutdown without migrating existing profile keys.
User Impact
The Unreleased notes now explain that persistent managed-browser logins survive graceful Browser and Gateway restarts. The entry thanks @TurboTheTurtle and links #96704 and #98284.
Evidence
git diff --check