[release/9.0.1xx] Restrict CI package publishing to Windows Release - #10502
Merged
Merged
Conversation
Adapt main commit 44cea09, including Debug suppression missing from this release branch. Preserve build and test coverage, signing, and per-leg diagnostic artifacts. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
nagilson
approved these changes
Sep 22, 2026
nagilson
enabled auto-merge
September 24, 2026 22:31
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.
Problem
Backport #10496 to
release/9.0.1xx. Multiple OS/configuration legs can publish the same packages to shared PackageArtifacts/BlobArtifacts containers.Solution
Semantically adapt the publishing restriction to this release branch rather than blindly cherry-picking main, because this branch lacks main's existing Debug suppression:
azure-pipelines-pr.yml, add Windows Debug suppression and disable publishing for every Linux/macOS configuration, leaving Windows Release publishing unchanged.azure-pipelines.yml, suppress publishing for non-Release Windows configurations on both PR and non-PR paths and for every Linux/macOS configuration.The CI wrappers inject Publish=true; the trailing /p:Publish=false property overrides it. Reuses the existing backport commit
203ebb5413c16b9fceb756c363f971744d64909dunchanged.Checks:
YAML-only change. Refreshed
origin/release/9.0.1xxand verified it remains an ancestor of the backport. Reused the existing release validator, restricted to this branch: 96 local YAML scenarios / 388 legs passed, covering public/internal, PR/non-PR, both pipeline definition names, main/release source-branch conditions, and Release/Debug/Checked configurations (including Debug-only). Only Windows Release publishes when present; Debug-only configurable runs have no publisher. All non-publishing expanded YAML and build-leg coverage were preserved. Also parsed both YAML files, checked wrapper argument ordering, verified exact two-file scope (+15 lines), and passed scopedgit diff --check.Validation uses a local expression evaluator, not Azure server expansion. External templates were not expanded; no dependencies installed, full builds, or live CI retries were performed.