Skip to content

chore(deps): update microsoft.build to 18.9.6 - #6585

Merged
thomhurst merged 1 commit into
mainfrom
renovate/microsoft.build
Aug 11, 2026
Merged

chore(deps): update microsoft.build to 18.9.6#6585
thomhurst merged 1 commit into
mainfrom
renovate/microsoft.build

Conversation

@thomhurst

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
Microsoft.Build (source) nuget minor 18.8.218.9.6
Microsoft.Build.Framework (source) nuget minor 18.8.218.9.6
Microsoft.Build.Utilities.Core (source) nuget minor 18.8.218.9.6

Release Notes

dotnet/msbuild (Microsoft.Build)

v18.9.6

What's Changed

New Contributors

Full Changelog: dotnet/msbuild@v18.8.2...v18.9.6


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file MINOR renovate-bot labels Aug 11, 2026
@thomhurst
thomhurst enabled auto-merge (squash) August 11, 2026 16:23
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e025edd5-99f8-4672-bd47-eef8ffecfa3c

📥 Commits

Reviewing files that changed from the base of the PR and between c1830bf and 6f43a52.

📒 Files selected for processing (4)
  • Directory.Packages.props
  • benchmarks/TUnit.SourceGenerator.Benchmarks/TUnit.SourceGenerator.Benchmarks.csproj
  • src/TUnit.Mocks.InternalsAccess.Tasks/TUnit.Mocks.InternalsAccess.Tasks.csproj
  • tests/TUnit.Mocks.InternalsAccess.Tests/TUnit.Mocks.InternalsAccess.Tests.csproj

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Aug 11, 2026

Copy link
Copy Markdown

Greptile Summary

The PR updates the repository’s Microsoft.Build package family from 18.8.2 to 18.9.6.

  • Updates the centrally managed Microsoft.Build.Utilities.Core version.
  • Aligns benchmark references to Microsoft.Build and Microsoft.Build.Framework.
  • Aligns the internals-access task and its in-process tests with the new Utilities.Core version.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
Directory.Packages.props Updates the centrally managed Microsoft.Build.Utilities.Core dependency to 18.9.6.
benchmarks/TUnit.SourceGenerator.Benchmarks/TUnit.SourceGenerator.Benchmarks.csproj Aligns compile-time-only Microsoft.Build and Microsoft.Build.Framework references with 18.9.6.
src/TUnit.Mocks.InternalsAccess.Tasks/TUnit.Mocks.InternalsAccess.Tasks.csproj Updates the MSBuild-host-provided Utilities.Core compile-time reference while continuing to exclude runtime assets.
tests/TUnit.Mocks.InternalsAccess.Tests/TUnit.Mocks.InternalsAccess.Tests.csproj Updates the test project’s in-process Utilities.Core runtime dependency to match the task’s compile-time version.

Reviews (4): Last reviewed commit: "chore(deps): update microsoft.build to 1..." | Re-trigger Greptile

@claude

claude Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Code Review

This PR is a mechanical Renovate dependency bump (Microsoft.Build / Microsoft.Build.Framework / Microsoft.Build.Utilities.Core 18.8.2 → 18.9.6) across Directory.Packages.props and three .csproj files.

Issue found

benchmarks/TUnit.SourceGenerator.Benchmarks/TUnit.SourceGenerator.Benchmarks.csproj:13 — this project bumps Microsoft.Build/Microsoft.Build.Framework to 18.9.6 but leaves the co-dependent Microsoft.NET.StringTools VersionOverride pinned at 18.8.2 on the next line. Microsoft.Build.Framework 18.9.6 requires Microsoft.NET.StringTools >= 18.9.6, so this now produces a reproducible restore failure:

error NU1605: Warning As Error: Detected package downgrade: Microsoft.NET.StringTools from 18.9.6 to 18.8.2
 -> TUnit.SourceGenerator.Benchmarks -> Microsoft.Build.Framework 18.9.6 -> Microsoft.NET.StringTools (>= 18.9.6)

I confirmed this locally by running dotnet restore on the project. Fix: bump the VersionOverride for Microsoft.NET.StringTools to 18.9.6 (or drop the override so it resolves transitively) alongside the other two package bumps in this file.

Everything else

Directory.Packages.props, src/TUnit.Mocks.InternalsAccess.Tasks/TUnit.Mocks.InternalsAccess.Tasks.csproj, and tests/TUnit.Mocks.InternalsAccess.Tests/TUnit.Mocks.InternalsAccess.Tests.csproj are clean, consistent version bumps — no other cross-referenced packages at risk there.

🤖 Generated with automated code review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a4713cf606

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

<PackageReference Include="BenchmarkDotNet" />
<PackageReference Include="Microsoft.Build" VersionOverride="18.8.2" ExcludeAssets="runtime" PrivateAssets="all" />
<PackageReference Include="Microsoft.Build.Framework" VersionOverride="18.8.2" ExcludeAssets="runtime" PrivateAssets="all" />
<PackageReference Include="Microsoft.Build" VersionOverride="18.9.6" ExcludeAssets="runtime" PrivateAssets="all" />

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Upgrade StringTools with the MSBuild packages

When restoring TUnit.SourceGenerator.Benchmarks, Microsoft.Build 18.9.6 requires the matching Microsoft.NET.StringTools dependency, but this project still directly pins StringTools to 18.8.2 on line 15. NuGet's direct-dependency-wins rule therefore selects the older version and reports an NU1605 package downgrade, preventing the benchmark project—and solution builds containing it—from restoring. Update the explicit StringTools override to 18.9.6 as part of this grouped upgrade.

Useful? React with 👍 / 👎.

@claude

claude Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Code Review

Re-reviewed after the previous round. This is a mechanical Renovate bump (Microsoft.Build / Microsoft.Build.Framework / Microsoft.Build.Utilities.Core → 18.9.6) across Directory.Packages.props and three .csproj files.

Previous issue resolved: the Microsoft.NET.StringTools VersionOverride mismatch in benchmarks/TUnit.SourceGenerator.Benchmarks/TUnit.SourceGenerator.Benchmarks.csproj (flagged in my earlier comment as causing a NU1605 downgrade restore error) has been fixed — it's now aligned at 18.9.6 alongside Microsoft.Build/Microsoft.Build.Framework.

I re-checked all Microsoft.Build*/StringTools references repo-wide and every pin is consistently 18.9.6. No cross-package version mismatches remain.

No issues found. Checked for bugs and CLAUDE.md compliance.

🤖 Generated with automated code review

@claude

claude Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Code Review

Re-reviewed the current state of this PR. This is a mechanical Renovate dependency bump (Microsoft.Build / Microsoft.Build.Framework / Microsoft.Build.Utilities.Core / Microsoft.NET.StringTools, all 18.8.218.9.6) across Directory.Packages.props and three .csproj files.

Verified:

  • All four package references are consistently pinned to 18.9.6 — no stale versions left behind.
  • The previously-flagged Microsoft.NET.StringTools downgrade mismatch in benchmarks/TUnit.SourceGenerator.Benchmarks/TUnit.SourceGenerator.Benchmarks.csproj (which would have caused a NU1605 restore error) remains fixed and aligned at 18.9.6.
  • The net472/net8.0 asset-compatibility comment in src/TUnit.Mocks.InternalsAccess.Tasks/TUnit.Mocks.InternalsAccess.Tasks.csproj is unchanged and not contradicted by this bump.
  • No CLAUDE.md rules are implicated (no source-gen/reflection dual-mode logic, no public API, no snapshot-affecting change, no hot-path code) — this diff contains no logic changes at all.

No issues found. Clean to merge.

🤖 Generated with automated code review

@claude

claude Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Code Review

Re-reviewed the current state of this PR (head 6f43a529, unchanged since the prior review). This remains a mechanical Renovate dependency bump — Microsoft.Build.Utilities.Core (and Microsoft.Build / Microsoft.Build.Framework in the benchmarks project) 18.8.218.9.6, applied consistently across Directory.Packages.props, benchmarks/TUnit.SourceGenerator.Benchmarks/TUnit.SourceGenerator.Benchmarks.csproj, src/TUnit.Mocks.InternalsAccess.Tasks/TUnit.Mocks.InternalsAccess.Tasks.csproj, and tests/TUnit.Mocks.InternalsAccess.Tests/TUnit.Mocks.InternalsAccess.Tests.csproj. No source, logic, or test code is touched.

Verified:

  • Repo-wide grep for 18.8.2 / stray Microsoft.Build version pins turns up nothing missed — the bump is applied everywhere it needs to be, and it also resolves a pre-existing inconsistency where Microsoft.NET.StringTools in the benchmarks project was already pinned to 18.9.6 while Microsoft.Build/Microsoft.Build.Framework lagged at 18.8.2.
  • src/TUnit.Mocks.InternalsAccess.Tasks/TUnit.Mocks.InternalsAccess.Tasks.csproj carries a load-bearing comment pinning the version to one that "ships both net472 and net8.0 assets" (the project multi-targets net472;net8.0). Confirmed on NuGet that 18.9.6 still ships net472 and netstandard2.0/net10.0 assets — same framework-support shape as 18.8.2, so this constraint still holds.
  • No packages.lock.json files exist in the repo that would need a matching update.

No correctness, design, or architectural concerns — there's no logic here to critique, just a version-string bump. This looks safe to merge as-is; no changes requested from my review.

This was referenced Aug 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file MINOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants