[release/v7.4] Update metadata.json to update the Latest attribute with a better name#26872
Open
TravisEz13 wants to merge 1 commit intoPowerShell:release/v7.4from
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request backports metadata property standardization from the main branch to release/v7.4, renaming the Latest property to PublishToChannels in the release metadata objects. This change corrects an earlier typo and standardizes the naming convention for controlling release channel publishing across pipeline templates.
Changes:
- Renamed
Latestproperty toPublishToChannelsinLTSReleaseandStableReleaseobjects inmetadata.json - Updated all pipeline template references to use the new
PublishToChannelsproperty name - Minor whitespace cleanup (removed trailing whitespace)
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tools/metadata.json | Renamed Latest to PublishToChannels in both LTSRelease and StableRelease objects |
| .pipelines/templates/channelSelection.yml | Updated to read PublishToChannels from metadata; reorganized variable declarations for clarity |
| .pipelines/templates/release-upload-buildinfo.yml | Updated to read PublishToChannels instead of Latest; removed trailing whitespace |
| .pipelines/templates/release-prep-for-ev2.yml | Updated to read PublishToChannels from LTSRelease; removed trailing whitespace |
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
2 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.4
Triggered by @TravisEz13 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
Pipeline metadata standardization for release channel selection; required for release automation.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Tested in previous release.
Risk
REQUIRED: Check exactly one box.
Release pipeline metadata changes; scoped and already exercised in a prior release.
Merge Conflicts
Resolved conflicts in .pipelines/templates/release-upload-buildinfo.yml and tools/metadata.json to preserve release/v7.4 values while switching to PublishToChannels.