Give the update prompt a real dialog with a link to what's new - #1
Merged
Conversation
The prompt was a native ask() box: one run-on line stating two version numbers and a question, with up to 400 characters of the release body pasted in. That body was fixed CI text telling the reader to download an installer from the assets — advice that makes sense on a release page and none at all inside an app that is about to do the downloading. There was no way to find out what had actually changed, which is the one thing worth knowing when deciding whether to install now. It is now a real dialog, styled like the others here. The heading names the version on offer and the subtitle says which one you are leaving and that your work stays open. Release notes appear in a scrollable panel, with boilerplate lines filtered out. A "What's new" link opens the full release page in a browser. Download progress moves into the dialog as a determinate bar, replacing toasts that could be missed behind other windows, and the buttons disable in place so nothing shifts under the pointer mid-download. The restart prompt now offers "Restart now" and "On next launch" rather than OK and Cancel, which said nothing about what declining would do. Releases carry GitHub's generated notes from now on, so the panel has real content to show instead of the same paragraph every time. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c64d18f4-c303-4cc3-8823-0e1f1b855817
jainnitin
pushed a commit
that referenced
this pull request
Aug 3, 2026
Carries the redesigned update dialog from #1, which is also the first version able to show its own release notes — the change is only visible from a version that predates it, so 1.0.4 is what earlier installs will be offered through the new prompt. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c64d18f4-c303-4cc3-8823-0e1f1b855817
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.
Why
The update prompt was a native
ask()box — one run-on line with two versionnumbers and a question, plus up to 400 characters of the release body pasted in.
That body was fixed CI text telling the reader to "download the installer for
your platform from the assets below" — advice that makes sense on a release
page and none at all inside an app that is about to do the downloading itself.
And there was no way to find out what had actually changed, which is the one
thing worth knowing when deciding whether to install now or later.
What changed
A real dialog, styled like the link and audit dialogs already in the app:
leaving and that your work stays open.
out so only substance shows.
that could sit behind another window unseen. Buttons disable in place, so
nothing shifts under the pointer mid-download.
of OK and Cancel, which said nothing about what declining would do.
Real release notes. The workflow now sets
generateReleaseNotes: true, soreleases carry GitHub's generated changelog and the panel has something worth
reading instead of the same paragraph every time.
Notes
open_external_urlalready allow-lists schemes, so the link cannot be used toopen anything local.
update_notes_opened, which shows whether anyone actuallywants the changelog — worth knowing before investing further here.
Verification
npm run preflightpasses: build, tests,cargo fmt, clippy with warningsdenied, workflow YAML, version agreement, credential scan.
the size it will appear.
release to offer, which the next version bump will provide.