PR Summary

This pull request includes several changes to the.pipelines directory, specifically in thePowerShell-Release-Official.yml,release-githubtasks.yml,release-publish-nuget.yml, anduploadToAzure.yml files. The changes focus on modifying pipeline stages, adding new stages, and updating tasks to improve the release process.

Pipeline Configuration Changes:

• Added new stagesPushGitTag andMakeDraftPublic inPowerShell-Release-Official.yml to push git tags and make GitHub release drafts public.
• Introduced variablesob_release_environment formsixbundle andPublishGitHubRelease stages to specify the release environment.[1][2]

Task and Job Updates:

• Replacedpwsh tasks withPowerShell@2 tasks inrelease-githubtasks.yml to streamline the installation and verification of PowerShell 7, and to clone repositories and set release versions.[1][2][3][4][5]
• Updatedrelease-publish-nuget.yml to usePowerShell@2 tasks for installing PowerShell 7, checking installation, and managing repository checkouts.[1][2]

Artifact Management:

• Added steps inuploadToAzure.yml to copy GitHub release files and NuGet packages to specific output directories for use in the release pipeline.

These changes aim to enhance the efficiency and reliability of the release process by adding new stages, updating tasks, and improving artifact 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 and is notWork in Progress.
  • If the PR is work in progress, please add the prefixWIP: or[ WIP ] to the beginning of the title (theWIP bot will keep its status check atPending while the prefix is present) and remove the prefix when the PR is ready.
• 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
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact onPowerShell Editor Services which is used in thePowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact onPSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact onEditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: