Release 0.20.16: clearer settings and private memory jobs - #197
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
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.
Release 0.20.16 includes the approved Settings follow-up (#196) and the merged memory component update (microsoft/amplifier-bundle-memory#17). Settings improves connection lifecycle, explicit host credential reuse, voice choices, notifications, activity detail and update reloads that preserve unsent chat drafts. Memory suggestions use Core sessions in a private runtime home and no longer require amplifier-app-cli. The development lock now resolves memory60b1241; moving main-source update policy is retained.
Validation: 179 combined backend, memory, Settings and release regressions; 327 frontend tests; versioned production build and repeat committed-assets comparison; wheel/source build verification. Fresh host dependency qualification selected Core2.0.1 and memory60b1241 without app-cli. The full Python suite is running locally and is not an automatic publication gate. Release CI independently qualifies package, frontend and real-worker lanes.
Memory's focused private-session tests passed; real-provider/standalone OS-service acceptance remains unverified and previously disclosed. Settings owner completed isolated browser acceptance, including draft-save failure. No live voice/audio or phone delivery claim. No manual Spark deployment or user-history changes.