{{ message }}
[release/v7.4.15] Fix the PSNativeCommandArgumentPassing test#27146
Merged
adityapatwardhan merged 1 commit intoPowerShell:release/v7.4.15from Apr 3, 2026
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Backports the fix from #27057 to ensure the PSNativeCommandArgumentPassing Pester test reflects the platform default behavior on Windows for the release/v7.4.15 branch, improving release automation reliability.
Changes:
- Simplifies the Windows-specific assertion to always expect
PSNativeCommandArgumentPassingto beWindows. - Removes the prior conditional logic that incorrectly asserted
Legacybased on a version-parse check.
daxian-dbw
approved these changes
Apr 2, 2026
744d928
into
PowerShell:release/v7.4.15
49 of 51 checks passed
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.

Backport of #27057 to release/v7.4.15
Triggered by @adityapatwardhan on behalf of @daxian-dbw
Original CL Label: CL-Test
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Backports a failing test fix needed for stable/LTS release automation reliability.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick applied cleanly with no conflicts onto release/v7.4.15. The change is scoped to test behavior and aligns with the already-merged fix on main.
Risk
REQUIRED: Check exactly one box.
The change only adjusts test behavior and does not modify shipping product runtime paths.