[release/v7.4.15] release-upload-buildinfo: replace version-comparison channel gating with metadata flags#27147
Merged
adityapatwardhan merged 1 commit intoPowerShell:release/v7.4.15from Apr 3, 2026
Conversation
…ith metadata flags (PowerShell#27074)
adityapatwardhan
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull request overview
Backport of main-branch change (#27074) to the release/v7.4.15 branch, updating the release buildinfo upload template to use tools/metadata.json publish flags (instead of version-tag comparisons) for channel gating and to always publish a version-specific buildinfo file for non-preview releases.
Changes:
- Replace stable channel gating based on release-tag/version comparisons with gating based on
StableRelease.PublishToChannelsmetadata flag. - Introduce
UploadVersionSpecific/VersionSpecificBuildInfoFileand upload{Major}-{Minor}.jsonfor non-preview (stable/LTS) builds. - Refactor preview/stable checks to use boolean flags derived from the buildinfo JSON file name.
TravisEz13
approved these changes
Apr 2, 2026
daxian-dbw
approved these changes
Apr 2, 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 #27074 to release/v7.4.15
Triggered by @adityapatwardhan on behalf of @app/copilot-swe-agent
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
Backports release buildinfo publishing logic to gate stable uploads via metadata flags and always publish version-specific non-preview buildinfo files.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick applied to release/v7.4.15 with one conflict in .pipelines/templates/release-upload-buildinfo.yml, resolved by preserving metadata-flag channel-gating behavior from the original PR. Verified resulting script includes UploadVersionSpecific variable wiring, stable gating by StableRelease.PublishToChannels, and upload task condition updates.
Risk
REQUIRED: Check exactly one box.
Scoped pipeline-template changes in a single file with behavior already validated in main; moderate risk due to release publishing path impact but no broad runtime code changes.
Merge Conflicts
Resolved one conflict in .pipelines/templates/release-upload-buildinfo.yml around obsolete StableReleaseTag comparison by keeping the metadata-flag guidance and logic from PR #27074.