Add PowerShell dependency to winget manifests#1549
Merged
Conversation
Re-applies the change from PR #1497 which was reverted in PR #1548. The original broke the workflow YAML because the PowerShell here-string content and closing tag had zero indentation, which terminated the YAML literal block scalar (run: |). Fixed by indenting the here-string body to match the block indentation level; YAML strips the leading spaces, leaving valid PowerShell with the closing tag at column 0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request re-applies the changes from PR #1497 (which was reverted in PR #1548) to add a PowerShell 7+ dependency to winget manifests. The previous implementation failed due to improper YAML indentation in the workflow file, causing the workflow to fail validation. This PR fixes the indentation issue by properly indenting the PowerShell here-string content to match the YAML block scalar requirements.
Changes:
- Modified winget workflow to output manifests to a directory instead of submitting directly
- Added PowerShell script logic to inject a
Dependencies.PackageDependenciesblock into the installer manifest - Fixed YAML indentation that caused the previous PR to fail
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
devm33
approved these changes
Feb 19, 2026
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
2 participants
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.
Re-applies the change from PR #1497 which was reverted in PR #1548.
What changed
The winget workflow now modifies the installer manifest to declare a dependency on PowerShell 7+ before submitting to the WinGet community repository.
What went wrong last time
The original PR's PowerShell here-string content and closing
"@had zero indentation inside the YAMLrun: |block. YAML literal block scalars require all content lines to be indented at least as much as the first content line (10 spaces here). The unindented lines terminated the block scalar, causing the workflow YAML to fail validation — the run had 0 jobs and never started.Fix
Indent the here-string body and closing
"@to match the surrounding YAML block indentation. YAML strips those leading spaces during parsing, producing valid PowerShell with"@at column 0 as required.