PR Summary

This pull request introduces several updates to the PowerShell release and packaging pipelines, primarily focused on improving MSIX Store publishing, channel selection logic, and build environment consistency. The changes enhance automation, streamline channel-specific publishing, and update configurations for better compatibility and maintainability.

MSIX Store Publishing and Channel Handling:

• Refactored the MSIX Store publishing pipeline to use separate publish tasks for LTS, Stable, and Preview channels, each with explicit conditions and configurations. Channel selection now relies on pipeline variables, improving clarity and maintainability. [1] [2]
• Updated StoreBroker configuration to include PDP.xml by default and set targetPublishMode to Immediate for faster publishing. [1] [2]
• Modified the pipeline to upload store failure logs on errors for better diagnostics. [1] [2]

Build and Validation Environment Improvements:

• Updated the Linux SDK validation image from Ubuntu 20.04 to Ubuntu 22.04 to ensure compatibility with newer dependencies.
• Added steps to import the build module and bootstrap the .NET environment before global tool and SDK validation, ensuring consistent build prerequisites across jobs. [1] [2] [3]

Pipeline Logic and Variable Handling:

• Improved channel selection logic in channelSelection.yml and related templates by referencing variables directly from previous pipeline stages, and corrected variable casing and usage for consistency. [1] [2]
• Adjusted changelog URL generation and tag parsing logic for both MSIX and NuGet release pipelines to better handle preview tags and formatting. [1] [2]

MSIX Packaging and Signing:

• Enhanced PDP XML and SBConfig file update scripts to handle XML namespaces correctly and provide verbose output for easier debugging. [1] [2]
• Added new variables for SDL credential scanning and TSA configuration files to improve security and compliance in the packaging process.

Pipeline Dependency and Variable Updates:

• Updated the MSIX publishing stage to depend on both setReleaseTagAndChangelog and PushGitTagAndMakeDraftPublic stages, and switched to using a variable for the release environment, increasing flexibility.

These changes collectively improve the reliability, maintainability, and traceability of the PowerShell release pipeline, especially regarding MSIX Store publishing and channel management.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed