Repository navigation
[FIX] Accept current and legacy Scoop installation metadata on Windows - #18
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
1 participant
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.
Windows setup stops after Scoop successfully installs Git because it checks only install.json. Current Scoop writes scoop-install.json.
Accept either metadata filename when detecting packages and verifying installation completion. Apply the same detection to the PSFzf migration and existing Windows package and font verification checks.
Validation: git diff --check passed. The reported installation was confirmed to contain scoop-install.json. PowerShell and Chezmoi are unavailable in the local environment, so Windows smoke and installation checks were not run locally. No new tests or documentation were added.