ci: Future proof GitHub merge queue branch trigger for release/* branches

[Copilot]

This PR makes the Azure Pipeline trigger future proof when creating new release/v* feature branches by updating trigger patterns to be more specific and targeted.

Changes Made

🔧 Pipeline Trigger Updates

• Main Pipeline (.pipelines/pipeline.yaml):

  • Updated PR trigger from release/* to release/v* for more precise matching
  • Added GitHub merge queue trigger gh-readonly-queue/release/v*/* for release branch merge queue support

• NPM Pipelines:

  • Updated .pipelines/npm/npm-scale-test.yaml PR trigger from release/* to release/v*
  • Updated .pipelines/npm/npm-conformance-tests.yaml PR trigger from release/* to release/v*

Technical Details

The new release/v* pattern will:

• ✅ Match version-based release branches: release/v1.0, release/v2.0.1, release/v1.0-alpha
• ❌ Skip non-version release branches: release/feature-branch, release/hotfix

Benefits

• Future-proof: New release/v* branches automatically trigger appropriate pipelines
• Precise: Only version-based release branches trigger builds, reducing unnecessary runs
• Consistent: All pipeline files use the same pattern for maintainability
• GitHub Integration: Merge queue operations now supported for release branches

Validation

All changes have been validated for:

• YAML syntax correctness
• Pattern matching behavior with test cases
• Consistency across all modified pipeline files

Fixes #3806.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[jpayne3506]

We are limiting the changes to only .pipelines/pipeline.yaml

[Copilot]

We are limiting the changes to only .pipelines/pipeline.yaml

Done. I've reverted the NPM pipeline changes and limited the scope to only .pipelines/pipeline.yaml as requested. The changes are now isolated to the main pipeline file only. (8ddc52d)

[jpayne3506]

Lets change release/v* to release/ in order to capture more scenarios

[Copilot]

Lets change release/v* to release/ in order to capture more scenarios

Updated the trigger patterns from release/v* to release/* to capture more release branch scenarios as requested. This now covers version-based branches, feature branches, and any other release branch formats. (1d57901)

[jpayne3506]

Logic:

• Pipeline triggers only call the current state of the given pipeline.yaml.
• All release/* pipelines have an old state of the pipeline which contains relevant testing to the given release train.
• Merge queue naming convention is locked to the target release/* branch, which matches our current mx structure.

[jpayne3506]

/azp run Azure Container Networking PR

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).