Chore: prepare Desktop v0.15.0 with clear release notes and the released CLI engine - #77
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.
Prepare Desktop v0.15.0 for publication. The changelog leads with the Microsoft Agent Framework migration and explains the browser, resumable plans, live command output, agent collaboration, personalization, and everyday fixes in user-facing language.
Pin the bundled engine to the exact released CLI v0.15.0 commit, e675782, verified against GitHub. Publish the curated release notes and installation instructions directly from the release pipeline, so users receive the readable overview instead of generated commit titles.
Validation: all 490 Desktop tests passed; Release build passed with no warnings or errors; self-contained Windows x64 publish succeeded. Windows Sandbox is unavailable on this machine, so fresh-machine launch and onboarding checks were not performed.