Repository navigation
Prepare Klip Windows release - #1
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 changed
Why
Klip needs to be a downloadable Windows application that a normal user can install and run without manually finding FFmpeg DLLs, configuring build tools, or granting administrator access. The release path also needs clear licensing, privacy behavior, reproducible dependencies, and a realistic hardware support boundary.
User impact
Users can install Klip per-user or run the portable ZIP, select a game/window or display, adjust desktop and microphone volume, save a replay, or record a session. Clips, recordings, settings, and logs use documented user folders and remain local.
Validation
git diff --checkpassed.Release notes
AMD and Intel encoder paths are implemented but still require the documented hardware checklist before they should be advertised as verified. Tagged public releases intentionally require repository code-signing secrets to avoid distributing an unsigned installer at scale. The EULA/privacy text should receive qualified legal review before broad commercial distribution.