Verify public WinGet installs - #13
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
OutageDeck.CLIfrom the officialwingetsourcealertscommand when the public package is version 0.1.3 or newerWhy
Microsoft's public source now contains
OutageDeck.CLIversion 0.1.2. This turns that catalog entry into a recurring end-user install check, so a broken package or missing command is caught after publication.Manual runs can require an exact expected version when a new manifest propagates. The command check is version-aware because the public source can legitimately lag the latest GitHub release.
Validation
source2.msixextracted and queried successfully forOutageDeck.CLI0.1.2outagedeckcommand aliasgit diff --checkpassedThe current pull request run is the clean public-install verification.