chore(deps): update microsoft.build to 18.6.3#5914
Conversation
thomhurst
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Dependency Update Review: Microsoft.Build 18.4.0 → 18.6.3
This is a routine Renovate bot PR updating three Microsoft.Build packages by two minor versions.
Changes look correct and consistent:
- : Updates centrally
- : Updates and via
VersionOverride
All three packages are pinned to the same version (18.6.3), which is important — version mismatches between Microsoft.Build, Microsoft.Build.Framework, and Microsoft.Build.Utilities.Core can cause subtle runtime failures.
Noteworthy 18.6.x improvements from the release notes that are relevant to TUnit's usage:
- Thread-safety fixes in
AssemblyTaskFactoryandWorkerNodeTelemetryData - Performance improvements for
ItemSpecModifiersandBuiltInMetadata(beneficial for the source generator benchmarks project) - Fixed
RecursiveDirmetadata loss in MT builds
No concerns — the ExcludeAssets="runtime" PrivateAssets="all" attributes on the benchmark project references are correctly preserved (these packages should only be used at build time, not shipped as runtime dependencies).
Good to merge.
There was a problem hiding this comment.
Dependency Update Review: Microsoft.Build 18.4.0 → 18.6.3
This is a routine Renovate bot PR updating three Microsoft.Build packages by two minor versions.
Changes look correct and consistent:
Directory.Packages.props: UpdatesMicrosoft.Build.Utilities.CorecentrallyTUnit.SourceGenerator.Benchmarks.csproj: UpdatesMicrosoft.BuildandMicrosoft.Build.FrameworkviaVersionOverride
All three packages are pinned to the same version (18.6.3), which is important — version mismatches between Microsoft.Build, Microsoft.Build.Framework, and Microsoft.Build.Utilities.Core can cause subtle runtime failures.
Noteworthy 18.6.x improvements from the release notes relevant to TUnit:
- Thread-safety fixes in
AssemblyTaskFactoryandWorkerNodeTelemetryData - Performance improvements for
ItemSpecModifiersandBuiltInMetadata(beneficial for the source generator benchmarks project) - Fixed
RecursiveDirmetadata loss in MT builds
No concerns — the ExcludeAssets="runtime" PrivateAssets="all" attributes on the benchmark project references are correctly preserved (these packages are build-time only and should not be shipped as runtime dependencies).
Safe to merge.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
thomhurst
force-pushed
the
renovate/microsoft.build
branch
from
557d422 to
bc83d1f
Compare
There was a problem hiding this comment.
Review: Microsoft.Build 18.4.0 → 18.6.3
Routine Renovate bot dependency update — no code logic changes, just version bumps across 3 files.
Changes verified:
Directory.Packages.props: Central version forMicrosoft.Build.Utilities.Corebumped correctlyTUnit.SourceGenerator.Benchmarks.csproj:Microsoft.BuildandMicrosoft.Build.Frameworkupdated viaVersionOverride
All three packages land on the same version (18.6.3) — version parity across the Microsoft.Build family is maintained, which avoids the subtle runtime failures that mismatched versions can cause.
Previous review comments (from earlier passes) raised no concerns, and nothing has changed to affect that assessment.
Build attributes preserved: ExcludeAssets="runtime" PrivateAssets="all" on the benchmark project references are intact — correct, since these are build-time-only dependencies.
No issues found. Safe to merge.
thomhurst
force-pushed
the
renovate/microsoft.build
branch
from
bc83d1f to
6aef6e3
Compare
There was a problem hiding this comment.
Re-review: Microsoft.Build 18.4.0 → 18.6.3
Revisiting after the previous review pass — no new changes have been made to the diff.
Previous review findings: No issues were raised, and that assessment still holds.
Diff summary (3 files, 3 additions, 3 deletions):
Directory.Packages.props: CentralMicrosoft.Build.Utilities.Coreversion:18.4.0→18.6.3TUnit.SourceGenerator.Benchmarks.csproj:Microsoft.BuildandMicrosoft.Build.FrameworkviaVersionOverride:18.4.0→18.6.3
Checks:
- All three
Microsoft.Buildfamily packages are pinned to the same version (18.6.3) — no cross-package version skew introduced. ExcludeAssets="runtime" PrivateAssets="all"on the benchmark project references are preserved — correct for build-time-only MSBuild dependencies.- No source code, tests, or snapshot files were modified.
This is a safe, mechanical dependency update. No concerns.
thomhurst
force-pushed
the
renovate/microsoft.build
branch
from
6aef6e3 to
fad2281
Compare
There was a problem hiding this comment.
Re-review: Microsoft.Build 18.4.0 → 18.6.3
No new changes since the last review pass.
Previous reviews (4 prior passes) all reached the same conclusion with no issues, and the diff is unchanged:
Directory.Packages.props: CentralMicrosoft.Build.Utilities.Coreversion bumped to18.6.3✓TUnit.SourceGenerator.Benchmarks.csproj:Microsoft.BuildandMicrosoft.Build.Frameworkupdated viaVersionOverrideto18.6.3✓
All three Microsoft.Build family packages remain in sync at 18.6.3, ExcludeAssets="runtime" PrivateAssets="all" is preserved on the benchmark project, and no source/test/snapshot files were touched.
Safe to merge.
thomhurst
force-pushed
the
renovate/microsoft.build
branch
from
fad2281 to
9d82bd7
Compare
2 participants
This PR contains the following updates:
18.4.0→18.6.318.4.0→18.6.318.4.0→18.6.3Release Notes
dotnet/msbuild (Microsoft.Build)
v18.6.3What's Changed
Includeattributes by @glektarssza in #132841357533by @dotnet-bot in #13394New Contributors
Full Changelog: dotnet/msbuild@v18.5.4...v18.6.3
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate.