fix(powershell): multiple Invoke-Expression fixes #8318
Merged
+24
−38
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
Contributor
alexsch01
commented
May 22, 2025
alexsch01
commented
- prevent pipeline input from using Invoke-Expression
- allow redirect operator to behave again by stripping redirects out from Invoke-Expression
mbtools
reviewed
May 24, 2025
|
@wraithgar it's ready! |
wraithgar
reviewed
May 27, 2025
wraithgar
approved these changes
May 27, 2025
Merged
This was referenced Jun 3, 2025
|
The v10 branch just had its dependencies updated, and we are likely going to want to roll out a backport release for v10. It would be nice to have the sum of the If you'd prefer you can give me an idea of what files to bring over and I can make the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.