-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Flip Stable PublishToChannel false for v7.5.X #27333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,5 +6,5 @@ | |
| "LTSReleaseTag" : ["v7.4.13"], | ||
| "NextReleaseTag": "v7.5.0-preview.4", | ||
| "LTSRelease": { "PublishToChannels": false, "Package": false }, | ||
| "StableRelease": { "PublishToChannels": true, "Package": true } | ||
| "StableRelease": { "PublishToChannels": false, "Package": true } | ||
|
||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting
StableRelease.PublishToChannelstofalsemakesChannelSelection.IsStableevaluate to false for non-preview builds, which leads to "No valid channel detected" failures in downstream release templates (e.g.,release-MSIX-Publish.ymlandpackage-store-package.yml) because they require exactly one channel to be true. To disable publishing without breaking the pipeline, consider separating "is stable build" from "publish stable to channels" (e.g., keep IsStable derived from the tag/build type and gate publish steps with a separate publish flag), or ensure the MSIX/Store publish stages/jobs are fully skipped when stable publishing is disabled.