Skip to content

[main] Bump Microsoft.Build.Framework and Microsoft.Build.Utilities.Core - #11969

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/multi-8dac25819c
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/multi-8dac25819c

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 16, 2026

Copy link
Copy Markdown
Contributor

Updated Microsoft.Build.Framework from 17.11.48 to 18.11.0.

Release notes

Sourced from Microsoft.Build.Framework's releases.

18.11.0

What's Changed

18.10.1

What's Changed

18.9.6

What's Changed

18.8.2

What's Changed

18.7.1

What's Changed

18.6.3

What's Changed

18.5.4

What's Changed

18.4.0

What's Changed

18.3.3

What's Changed

18.0.2

What's Changed

17.14.28

What's Changed

Description has been truncated

Bumps Microsoft.Build.Framework from 17.11.48 to 18.11.0
Bumps Microsoft.Build.Utilities.Core from 17.11.48 to 18.11.0

---
updated-dependencies:
- dependency-name: Microsoft.Build.Framework
  dependency-version: 18.11.0
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: Microsoft.Build.Utilities.Core
  dependency-version: 18.11.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Copilot AI balanced review requested due to automatic review settings October 16, 2026 06:59
@dependabot dependabot Bot added the dependencies Updates to dependency manifests. label Oct 16, 2026
@github-actions github-actions Bot added the state/needs-review Awaiting review from the team. label Oct 16, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The major dependency upgrade needs compatibility validation against supported target frameworks and older MSBuild hosts.

0 open findings

What changed in this PR

Updates the shared MSBuild dependencies used by TestFx’s build and packaging integration.

Changes:

  • Raises MicrosoftBuildVersion from 17.11.48 to 18.11.0, updating Microsoft.Build.Framework and Microsoft.Build.Utilities.Core together.

Test-value evidence: No execution evidence was supplied for this revision; compatibility with supported target frameworks and older MSBuild hosts remains unverified.

File Description
Directory.Packages.props Updates the central MSBuild package version.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Copilot AI commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

One or more custom setup steps configured for this repository failed during this Copilot code review run:

Build the repository

Setup steps run before each review. If the review above is missing context, or no review was posted at all, the failing step above may be the cause. See the workflow run for failure details, fix your setup steps configuration, and re-request a review.

Note

You can configure setup steps for Copilot code review separately from Copilot cloud agent with a copilot-code-review.yml file. Read the docs for details.

@dependabot @github

dependabot Bot commented on behalf of github Oct 16, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/nuget/multi-8dac25819c branch October 16, 2026 07:20
@github-actions github-actions Bot removed the state/needs-review Awaiting review from the team. label Oct 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Final test-triage resolution — Azure Pipelines build 1637865

This is a final resolution; the aggregate build (1637865) has completed.

Root cause: build compilation failure in this PR, not a test-infrastructure or flaky-test issue.

The Windows Debug, Windows Release, and Linux Release legs' Build task failed with compiler errors:

Microsoft.NET.StringTools 18.11.0-1.26512.6 doesn't support net8.0/net9.0/net10.0 and has not been tested with it.
Microsoft.Build.Framework 18.11.0-1.26512.6 doesn't support net8.0/net9.0/net10.0 ...
Microsoft.Build.Utilities.Core 18.11.0-1.26512.6 doesn't support net8.0/net9.0/net10.0 ...

This directly matches the PR's own change (bumping Microsoft.Build.Framework and Microsoft.Build.Utilities.Core, which pulled in transitive Microsoft.NET.StringTools 18.11.0). Those packages declare they are untested/unsupported on net8.0/net9.0/net10.0, so the Build task fails before any package is produced.

That build failure cascades into all 11 downstream "test" failures in the Windows application-model acceptance job (MSTest.Acceptance.IntegrationTests.WindowsApplicationModelPackageTests.*, both CTRF and JUnit reports, including the two-attempt retries of NativeSdkEnvironment_AlignsSdkPathsAndPreservesSharedTooling): every one throws System.InvalidOperationException: Was expecting to find a single NuGet package named 'MSTest.TestFramework.' ... but found 0, because artifacts/packages/Release/Shipping is empty — the packing step never produced packages, since the compile step failed first. The two tests that did pass (PackagedHostFilterTests_AreSelectedByApplicationModelJob, ModernUwp_ResolvedAssetsRequireMatchingFrameworkAndSpecializedPayloads) don't depend on the missing package lookup.

Assessment: This is an ordinary build/compile failure directly caused by the dependency bump under review, not a test defect, flake, or CI infrastructure regression. No retry recovered any of these failures (both JUnit attempts for the native-SDK test failed identically), consistent with a deterministic compile-time incompatibility rather than flakiness.

No issue is warranted — the fix belongs in this PR (pin compatible Microsoft.Build.*/Microsoft.NET.StringTools versions, or address the TFM-support warning before bumping) rather than in test infrastructure. Since the PR is closed, no further action is needed on this build.

🤖 Automated content by GitHub Copilot. Generated by the Pipeline Test Triage workflow. · copilot · auto · 64.3 AIC · ⌖ 5.36 AIC · ⊞ 9.9K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Updates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants