Skip to content

Flip Stable PublishToChannel false for v7.5.X#27333

Merged
jshigetomi merged 1 commit into
PowerShell:release/v7.5.6from
jshigetomi:updatemetadata
Apr 22, 2026
Merged

Flip Stable PublishToChannel false for v7.5.X#27333
jshigetomi merged 1 commit into
PowerShell:release/v7.5.6from
jshigetomi:updatemetadata

Conversation

@jshigetomi
Copy link
Copy Markdown
Collaborator

@jshigetomi jshigetomi commented Apr 22, 2026

PR Summary

This pull request makes a small change to the release configuration in the tools/metadata.json file. The update disables publishing to channels for stable releases, while still allowing package creation.

PR Context

This is to prevent 7.5.X which from publishing to stable channels.

PR Checklist

@jshigetomi jshigetomi added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Apr 22, 2026
@jshigetomi jshigetomi marked this pull request as ready for review April 22, 2026 20:58
@jshigetomi jshigetomi requested a review from a team as a code owner April 22, 2026 20:58
Copilot AI review requested due to automatic review settings April 22, 2026 20:58
@jshigetomi jshigetomi merged commit 44feecc into PowerShell:release/v7.5.6 Apr 22, 2026
37 of 45 checks passed
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the release metadata used by pipeline templates to disable publishing stable releases to channel-based destinations while still allowing package creation.

Changes:

  • Flip StableRelease.PublishToChannels from true to false in tools/metadata.json.

Comment thread tools/metadata.json
"NextReleaseTag": "v7.5.0-preview.4",
"LTSRelease": { "PublishToChannels": false, "Package": false },
"StableRelease": { "PublishToChannels": true, "Package": true }
"StableRelease": { "PublishToChannels": false, "Package": true }
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setting StableRelease.PublishToChannels to false makes ChannelSelection.IsStable evaluate to false for non-preview builds, which leads to "No valid channel detected" failures in downstream release templates (e.g., release-MSIX-Publish.yml and package-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.

Suggested change
"StableRelease": { "PublishToChannels": false, "Package": true }
"StableRelease": { "PublishToChannels": true, "Package": true }

Copilot uses AI. Check for mistakes.
Comment thread tools/metadata.json
"NextReleaseTag": "v7.5.0-preview.4",
"LTSRelease": { "PublishToChannels": false, "Package": false },
"StableRelease": { "PublishToChannels": true, "Package": true }
"StableRelease": { "PublishToChannels": false, "Package": true }
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR title/description mention preventing 7.5.x from publishing to stable channels, but this flag disables stable-channel publishing for all stable (non-preview) builds produced from this branch. If the intent is specific to 7.5.x only, it may be worth confirming this PR targets the correct release branch and that disabling stable publishing here won’t unintentionally affect other stable servicing releases that use the same pipeline config.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants