[release/v7.5] Added Deploy Box Product Pathway to GitHub Release and NuGet Release Pipelines #24595
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 #24583
This pull request includes significant changes to the
.pipelines/PowerShell-Release-Official.yml
file to update container images, modify dependencies, and add new stages. Additionally, new templates for downloading packages and checking out repositories have been introduced.Key changes include:
Container Image Updates:
WindowsContainerImage
to useltsc2022
instead ofltsc2019
.Dependency Modifications:
resources
section to include a newrelease
category and updatedWindowsHostVersion
to2022
withNetlock
network.New Stages and Dependencies:
DownloadPackages
,PublishGitHubRelease
, andPushGitTagAndMakeDraftPublic
. Each new stage includes its respective jobs and dependencies. [1] [2]Template Additions:
release-download-packages.yml
for downloading various package types, including Linux, Windows, and macOS packages.release-checkout-pwsh-repo.yml
for checking out the PowerShell repository, including a script to handle branch names and clone the repository.Refactoring GitHub Tasks:
release-githubtasks.yml
to use therelease
pool and added new variables and steps to streamline the GitHub release process. [1] [2] [3]