Repository navigation
chore: prepare USBGuardGUI 0.2.0 - #62
Merged
Merged
Conversation
Signed-off-by: onyks-os <129986281+onyks-os@users.noreply.github.com>
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.
Prepare USBGuardGUI 0.2.0 with rule/device previews, device details, private local history and validated desktop behavior, together with the zbus/SNI migration and application-wide coverage gate.
Synchronize Cargo.toml/Cargo.lock, the Arch package version, AppStream release metadata and generated changelog; fix the changelog comparison links and assign all four completed product milestones to 0.2.0. No additional languages or AUR publication are included.
Validation: Rust suite and lint passed in a private namespace; dependency-policy, existing catalogue and coverage-tool tests passed; AppStream validation and strict MkDocs passed. Current-head CI must also pass before merge. A release candidate will then run the reproducible-package and installed Flatpak gates; downloaded signatures/checksums and a native guest installation must pass before the stable tag at the same commit.