PR Summary

This pull request introduces significant improvements to the PowerShell build pipeline by making the build and signing process more flexible and robust. The main changes allow the pipeline to distinguish between official and non-official builds, dynamically select templates, and provide more granular handling of code signing. These updates make it easier to manage different build scenarios and improve the reliability and clarity of signing checks.

Pipeline configuration and template selection:

• Added theOfficialBuild boolean parameter andvPackName parameter to.pipelines/PowerShell-vPack-Official.yml, enabling selection between official and non-official build templates and scenarios.
• Dynamically set the pipeline template via the newtemplateFile variable, allowing the pipeline to choose betweenMicrosoft.Official.yml andMicrosoft.NonOfficial.yml based on the build type.[1][2]

Build and artifact handling:

• Refactored build steps to create a dedicated symbols folder per architecture, set thePowerShellRoot andRuntime variables, and improved output and artifact directory management for clarity and consistency.[1][2][3]

Code signing improvements:

• Updated.pipelines/templates/obp-file-signing.yml andtools/packaging/packaging.psm1 to accept and propagate theOfficialBuild parameter, allowing signing logic to distinguish between official and non-official builds and adjust signature checks and warnings accordingly.[1][2][3][4][5][6]
• Made the signing profile configurable via theSigningProfile parameter, supporting different signing requirements for official and non-official builds.

These changes collectively improve the maintainability and reliability of the pipeline, especially around build type selection and code signing.

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 aDraft 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