[release/v7.4.17] Skip Store Publish when No Channel Seleceted#27571
Merged
SeeminglyScience merged 1 commit intoJun 9, 2026
Conversation
Co-authored-by: Justin Chung <chungjustin@microsoft.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR backports the release pipeline change to gracefully skip Microsoft Store package creation/publish when no release channel (LTS/Stable/Preview) is selected, preventing pipeline failures for “no-channel” runs on release/v7.4.17.
Changes:
- Add “no channel selected” handling to skip Store package creation and set
SkipStorePublishto prevent downstream Store upload steps from running. - Add task-level conditions in the Store publish template so Store JSON manipulation/validation steps don’t run when no channel is selected.
- Gate the StoreBroker package upload step on
SkipStorePublishto avoid failing on missing outputs.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.pipelines/templates/release-MSIX-Publish.yml |
Adds channel-based conditions to avoid running Store publish prep steps when no channel is selected. |
.pipelines/templates/package-store-package.yml |
Adds warning + skip logic (including SkipStorePublish) and conditions to avoid Store package creation/upload when no channel is selected. |
SeeminglyScience
approved these changes
Jun 8, 2026
adityapatwardhan
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 of #27334 to release/v7.4.17
Triggered by @TravisEz13 on behalf of @jshigetomi
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Prevents pipeline failure when no release channel (LTS/Stable/Preview) is selected by skipping Store package creation and publish steps gracefully.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Pipeline tested by running without a channel selection to verify it skips gracefully instead of failing.
Risk
REQUIRED: Check exactly one box.
Pipeline-only change that adds graceful skip logic when no channel is selected. No runtime code changes.