[release/v7.6] Update metadata.json to update the Latest attribute with a better name#26708
Merged
daxian-dbw merged 1 commit intoPowerShell:release/v7.6from Jan 21, 2026
Conversation
daxian-dbw
added
the
CL-BuildPackaging
daxian-dbw
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull request overview
This PR backports changes from #26380 that rename the metadata property "Latest" to "PublishToChannels" for better clarity in build/release tooling. It also updates version numbers in metadata.json for the v7.6 release branch.
Changes:
- Renamed "Latest" property to "PublishToChannels" in metadata.json for both LTSRelease and StableRelease objects
- Updated all pipeline template references to use the new property name
- Updated version tags in metadata.json (StableReleaseTag, PreviewReleaseTag, ReleaseTag, LTSReleaseTag, NextReleaseTag)
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tools/metadata.json | Updated version numbers and renamed "Latest" property to "PublishToChannels" in LTSRelease and StableRelease objects |
| .pipelines/templates/release-upload-buildinfo.yml | Updated property references from metadata.StableRelease.Latest and metadata.LTSRelease.Latest to use PublishToChannels |
| .pipelines/templates/release-prep-for-ev2.yml | Updated property reference from metadata.LTSRelease.Latest to metadata.LTSRelease.PublishToChannels; includes minor whitespace cleanup |
| .pipelines/templates/channelSelection.yml | Updated property references to use PublishToChannels and reorganized code to group variable assignments more logically |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jshigetomi
approved these changes
Jan 21, 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
3 participants
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 #26380 to release/v7.6
Triggered by @daxian-dbw on behalf of @adityapatwardhan
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
Customer Impact
Build and release pipeline improvement. Updates metadata property naming from 'Latest' to 'PublishToChannels' for better clarity. This only affects internal build tooling.
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
The fix has been tested in the original PR. Changes can be verified by running the release pipelines and confirming they correctly read the 'PublishToChannels' property from metadata.json. All pipeline template references have been updated to use the new property name.
Risk
REQUIRED: Check exactly one box.
The changes standardize metadata property naming in build/release pipelines by renaming 'Latest' to 'PublishToChannels'. All references in pipeline templates have been updated consistently. This is internal tooling only and doesn't affect product code.
Merge Conflicts
Merge conflict in tools/metadata.json due to version number differences between branches. Resolved by accepting the cherry-picked changes (both version updates and property rename).