Fix Windows build ZIP packaging#16299
Conversation
|
Is there a good way to test this change locally? Or at least before shipping? |
TravisEz13
left a comment
There was a problem hiding this comment.
Just saying requesting changes so no one else merges until I verify moving to 7 doesn't break something.
Looks good, we need to run a test build. I started build 219728 (not public, just for me to find it.). Assuming it passes, this should be good to merge at that point. We have a lot of changes to the build system with GA. This might take some time. Ping me periodically if it takes more than a week.
Short answer, no. I'm confident it will work, but not 100%. There might be minor changes required is some of scripts, but the environment is quite specialized for releasing Microsoft software and getting a good repro locally would be difficult. Some of the major gotchas are, json serialization varies between Windows PowerShell and PowerShell 7 and Some variable don't exist in Windows PowerShell. |
|
@kondratyev-nv Thank you for your help! |
|
We have already branched for the 7.2 release. I'm marking this for Back port consider for each branch we maintain, but I only tested against master. |
|
🎉 Handy links: |
|
🎉 Handy links: |
|
/backport to release/v7.0.11 |
|
Started backporting to release/v7.0.11: https://github.com/PowerShell/PowerShell/actions/runs/2242798277
|
|
@TravisEz13 an error occurred while backporting to release/v7.0.11, please check the run log for details! Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between release/v7.0.11 and backport/pr-16299-to-release/v7.0.11"} |
|
Already backported to 7.0: 3b6604f |
PR Summary
Fixes #16261
PR Context
Fix shell for calling
PowerShellPackage.ps1in CI for packaging step.