chore(deps): update dependency microsoft.visualstudio.threading.analyzers to 17.14.15

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.VisualStudio.Threading.Analyzers (source)	nuget	minor	17.13.61 → 17.14.15

---

Release Notes

microsoft/vs-threading (Microsoft.VisualStudio.Threading.Analyzers)

v17.14.15

What's Changed

Fixes

• Fix VSTHRD110 false negative in local functions of async methods by @​AArnott in #​1385
• Fix a race condition which leads product to hang by @​lifengl in #​1426
• Switch from build to buildTransitive for analyzer package by @​AArnott in #​1434

Enhancements

• Create a Microsoft.VisualStudio.Threading.Only package by @​AArnott in #​1429
• Get !dumpasync ready for Azure Watson by @​AArnott in #​1380

Dependency updates

• Update dependency System.Runtime.CompilerServices.Unsafe to 6.1.0 by @​renovate in #​1406
• Update Included in .NET runtime to v8 (major) by @​renovate in #​1408
• Update dependency System.Memory to 4.6.0 by @​renovate in #​1402
• Update dependency System.Threading.Tasks.Extensions to 4.6.0 by @​renovate in #​1407
• Update dotnet monorepo to 4.13.0 by @​renovate in #​1424
• Update dependency Microsoft.Bcl.AsyncInterfaces to v9 by @​renovate in #​1438

Full Changelog: microsoft/vs-threading@v17.13.2...v17.14.15

---

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 this update again.

---

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

---

This PR has been generated by Mend Renovate.

[claude]

Dependency Update Review: Microsoft.VisualStudio.Threading.Analyzers 17.13.61 → 17.14.15

This is a clean, minimal bump — single line in Directory.Packages.props, analyzer-only (no runtime impact).

What's in this update

Bug fixes worth noting:

• VSTHRD110 false negative in local functions of async methods is now correctly caught. Since TUnit explicitly prohibits .Result/.GetAwaiter().GetResult() (per CLAUDE.md), this tightening is beneficial — it may surface previously-missed violations in local async functions across the codebase.
• A race condition fix that could cause hangs.

Behavioral change to be aware of:

• The package switches from build to buildTransitive targets. This means analyzer rules will now flow transitively to projects that reference this package indirectly. In practice this is unlikely to cause issues since the analyzer is a dev-time tool, but worth knowing if any downstream consumers of TUnit packages start seeing new VSTHRD warnings.

Assessment

Safe to merge. The VSTHRD110 improvement aligns well with TUnit's strict no-blocking-async policy and may catch issues that were previously silently missed in local functions.

[codacy-production]

Up to standards ✅

🟢 Issues0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics0 complexity

Metric	Results
Complexity	0

View in Codacy

_{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.}