[release/v7.4.20] Fix install dotnet for non early access release - #27926
Merged
Aditya Patwardhan (adityapatwardhan) merged 1 commit intoSep 1, 2026
Conversation
Aditya Patwardhan (adityapatwardhan)
requested a review
from a team
as a code owner
September 1, 2026 01:34
Aditya Patwardhan (adityapatwardhan)
added
the
CL-BuildPackaging
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Copilot started reviewing on behalf of
Aditya Patwardhan (adityapatwardhan)
September 1, 2026 01:35
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Backports pipeline template updates to release/v7.4.20 to ensure release validation jobs initialize version variables early and avoid forcing non-early-access .NET installation into a non-default OneBranch restore phase configuration.
Changes:
- Insert
SetVersionVariables.ymlimmediately after checkout soRepoRoot/version variables are initialized before subsequent release-tag/container setup. - Update
install-dotnet.ymlinvocation to setob_restore_phase: falseonly for early-access builds (non-early-access uses the template’s default behavior).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .pipelines/templates/release-validate-globaltools.yml | Initializes version variables earlier; gates ob_restore_phase: false to early-access .NET install path. |
| .pipelines/templates/release-validate-fxdpackages.yml | Same adjustments as globaltools for FXD package validation jobs. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Patrick Meinecke (SeeminglyScience)
approved these changes
Sep 1, 2026
Aditya Patwardhan (adityapatwardhan)
merged commit Sep 1, 2026
a7fec0a
into
PowerShell:release/v7.4.20
36 checks passed
Aditya Patwardhan (adityapatwardhan)
deleted the
backport/release/v7.4.20/27892-9fa54b610
branch
September 1, 2026 01:40
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 #27892 to release/v7.4.20
Triggered by Aditya Patwardhan (@adityapatwardhan) on behalf of Aditya Patwardhan (@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
Corrects release validation pipeline setup by initializing version variables before release tag/container setup and limiting ob_restore_phase: false to early-access builds, so non-early-access release validation installs .NET with the intended defaults.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Cherry-pick completed cleanly against the latest fetched upstream/release/v7.4.20. Verified the delta contains only the two intended release validation templates, git diff --check passes, tracked files contain no conflict markers, Prettier 3.6.2 parses both changed YAML files successfully, and the worktree is clean.
Risk
REQUIRED: Check exactly one box.
This changes release validation pipelines for framework-dependent packages and global tools across release builds. The change is narrowly scoped to two template invocations and was validated for YAML syntax and exact diff content, but pipeline changes can affect release validation on multiple platforms.