Repository navigation
Auto-update: check GitHub Releases and install a verified setup - #17
Merged
Merged
Conversation
Xarishark
enabled auto-merge
November 8, 2026 18:58
Xarishark
disabled auto-merge
November 8, 2026 19:02
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 and why
Now that the repo is public, Director can find and install new versions itself, without asking you to download setup again.
Window: when it opens, Director asks GitHub's
releases/latestendpoint for the newest version (through WinHTTP, using the system proxy). If that version is newer, a notice above every page offers Install update, What's new and a close button. If the check fails, it's only logged, so offline startups stay quiet.Install update: Director downloads
Director-x64-setup.exeto%TEMP%\Director-updateand runs it only if both of these hold:digestGitHub reports for that file;Download progress shows as a real progress bar in the window. Director then starts setup with
/passive(only setup's progress window, no clicks) and the currentDesktopShortcutchoice, read fromHKLM\Software\Director\Installer, and closes so setup can replace the files. A hiddencmdwaits for setup and reopens Director only if setup exits with 0; a cancelled admin prompt (1602) or a pending restart (3010) leaves it closed. Director refuses to update while there are unsaved drafts or staged Now changes.Copies outside
Program Files\Director(builds from source) show Download, which opens the release page instead.Options → About: a switch for the startup check (new preference
check_for_updates, on by default; preferences stay format version 1) and a Check for updates button.CLI:
director updatereports whether a newer version exists;director update --installdownloads, verifies and starts setup. Commands never check on their own, so shortcuts and Stream Deck buttons stay offline.Docs: INSTALL (Update section), README, SECURITY (updates added to the scope) and an Unreleased CHANGELOG entry.
For reviewers: copies on 0.13.0 don't have this, so users update by hand once. No new dependencies; this uses the existing
sha2,serde_jsonandwindowsWinHTTP/Registry features. Tests and preview fixtures never contact GitHub, because the startup check iscfg(not(test)).Checks
cargo fmt --all -- --checkcargo clippy --locked --all-targets -- -D warnings(run locally without--lockedon the newer toolchain; CI runs the pinned version)cargo test --locked -- --test-threads=1(162 lib + 22 app passed locally)THIRD_PARTY_LICENSES.mdregenerated if dependencies changed (no dependency changes)Tested by hand
director updateagainst the real GitHub printed "Director 0.13.0 is up to date."update::tests::downloads_and_verifies_the_latest_setupdownloaded the real v0.13.0 setup through GitHub's redirect, and the checksum matched.cmdwaiter, tested with stand-in programs: exit 0 reopens; 1602 and 3010 don't; paths with spaces work.