release: v0.5.2#353
Merged
Merged
Conversation
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
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
Patch release rolling up the merged work since v0.5.1:
(session_id, msg_uuid)+ UNIQUE INDEXScanStatusBanner)Why
Cuts a patch version so the bulk-purge UX fix from #344 actually reaches users — the 60s → main-thread-responsive arc only matters in real installs. Same release also picks up the append-only sync semantic that makes Security Scan state durable across the natural "re-sync the session after a new turn" lifecycle.
No schema or IPC contract changes beyond what already landed in v0.5.1's migration v13 → v0.5.2's migration v14. Schema migration is idempotent and runs once on first launch.
Verification
Each underlying PR's CI was green at merge; this release branch only bumps
versionin 6package.jsonfiles. No code changes ride along.