[release/v7.4.16] Correct Variable Template Reference in NonOfficial Pipeline Templates#27428
Merged
adityapatwardhan merged 1 commit intoMay 15, 2026
Conversation
…PowerShell#27275) Co-authored-by: Justin Chung <chungjustin@microsoft.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Backport of #27275 to release/v7.4.16 that fixes broken ADO pipeline template references by switching from the invalid relative form ./pipelines/templates/... to the absolute, repo-root–anchored form /.pipelines/templates/...@self. Also updates the SplitADOPipelines agent doc to codify the absolute-path convention.
Changes:
- Correct template paths in all five
.pipelines/NonOfficial/*.ymlpipeline entry files (and one stages template) to use/.pipelines/templates/...@self. - Update
.github/agents/SplitADOPipelines.agent.mdto require the absolute template path convention and reflect the actual directory layout (variables/,stages/).
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| .pipelines/templates/stages/PowerShell-vPack-Stages.yml | Fix SetVersionVariables.yml include to use absolute /.pipelines/...@self path. |
| .pipelines/NonOfficial/PowerShell-vPack-NonOfficial.yml | Fix variables and stages template includes to absolute paths. |
| .pipelines/NonOfficial/PowerShell-Release-NonOfficial.yml | Fix variables and stages template includes to absolute paths. |
| .pipelines/NonOfficial/PowerShell-Release-Azure-NonOfficial.yml | Fix variables template include to absolute path. |
| .pipelines/NonOfficial/PowerShell-Packages-NonOfficial.yml | Fix variables and stages template includes to absolute paths. |
| .pipelines/NonOfficial/PowerShell-Coordinated_Packages-NonOfficial.yml | Fix variables and stages template includes; also adds WindowsHostVersion.Version: 2022. |
| .github/agents/SplitADOPipelines.agent.md | Document the absolute template path convention; update example paths to current layout. |
SeeminglyScience
approved these changes
May 15, 2026
1876dcd
into
PowerShell:release/v7.4.16
40 checks passed
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 #27275 to release/v7.4.16
Triggered by @adityapatwardhan on behalf of @jshigetomi
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
Fixes broken template references in NonOfficial pipeline YAML files, ensuring pipelines run successfully in release branches. Required for CI/CD health.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
N/A - Pipeline YAML and documentation changes only. Verified by successful pipeline runs on main branch. No code changes affecting product binaries.
Risk
REQUIRED: Check exactly one box.
Only updates pipeline YAML template references and documentation. No impact on product code or runtime behavior. Minimal risk to release branch stability.