V10.1.4/service update

[codebelt-aicia]

This is a service update that focuses on package dependencies.

Automated changes:

• Codebelt/Cuemon package versions bumped to latest compatible
• PackageReleaseNotes.txt updated for v10.1.4
• CHANGELOG.md entry added for v10.1.4

Note: Third-party packages (Microsoft.Extensions.*, BenchmarkDotNet, etc.) are not auto-updated.
Use Dependabot or manual updates for those.

Generated by codebelt-aicia
Triggered by: xunit @ 11.1.0

[greptile-apps]

Greptile Summary

This is a routine automated service update bumping Codebelt/Cuemon package dependencies and recording the v10.1.4 release across release notes and the changelog. No source code changes are included.

• Directory.Packages.props: Codebelt.Extensions.Xunit/.App bumped from 11.0.10 to 11.1.0 (triggered by the new xunit release); all Cuemon.* packages bumped from 10.5.2 to 10.5.3; third-party packages (Newtonsoft.Json, Microsoft.*, xunit.*, etc.) intentionally left unchanged.
• Four PackageReleaseNotes.txt files and CHANGELOG.md updated consistently to reflect the v10.1.4 release.

Confidence Score: 4/5

Safe to merge — all changes are limited to package version pins and release documentation with no source code modifications.

The only functional change is bumping well-scoped internal dependencies; the Codebelt.Extensions.Xunit minor-version jump (11.0 → 11.1) is the one area worth a quick sanity check, as minor bumps can occasionally surface breaking test-infrastructure changes. The trailing-newline removal in Directory.Packages.props is cosmetic but could produce noisy future diffs.

Directory.Packages.props — the Codebelt.Extensions.Xunit minor version bump and the missing trailing newline are worth a glance before merging.

Important Files Changed

Filename	Overview
Directory.Packages.props	Package version bumps: Codebelt.Extensions.Xunit/App 11.0.10→11.1.0 and all Cuemon.* packages 10.5.2→10.5.3; trailing newline removed from the file
CHANGELOG.md	Adds v10.1.4 entry dated 2026-06-05 describing the dependency update service release
.nuget/Codebelt.Extensions.Newtonsoft.Json/PackageReleaseNotes.txt	Prepends v10.1.4 release note entry for .NET 10, .NET 9, and .NET Standard 2.0
.nuget/Codebelt.Extensions.AspNetCore.Newtonsoft.Json/PackageReleaseNotes.txt	Prepends v10.1.4 release note entry for .NET 10 and .NET 9
.nuget/Codebelt.Extensions.AspNetCore.Mvc.Formatters.Newtonsoft.Json/PackageReleaseNotes.txt	Prepends v10.1.4 release note entry for .NET 10 and .NET 9
.nuget/Codebelt.Extensions.Newtonsoft.Json.App/PackageReleaseNotes.txt	Prepends v10.1.4 release note entry for .NET 10 and .NET 9

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Trigger: Codebelt.Extensions.Xunit @ 11.1.0"] --> B["Directory.Packages.props"]
    B --> C["Codebelt.Extensions.Xunit/App\n11.0.10 → 11.1.0"]
    B --> D["Cuemon.* packages\n10.5.2 → 10.5.3"]
    B --> E["Third-party packages\n(unchanged)"]
    A --> F["Version bump: v10.1.4"]
    F --> G["CHANGELOG.md"]
    F --> H["PackageReleaseNotes.txt ×4"]

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
Directory.Packages.props:30-31
The file no longer ends with a newline after this change. Most editors and POSIX tools expect a trailing newline, and its absence can cause noisy diffs in future PRs.

```suggestion
  </ItemGroup>
</Project>
```

_{Reviews (1): Last reviewed commit: "V10.1.4/service update" | Re-trigger Greptile}

[greptile-apps]

The file no longer ends with a newline after this change. Most editors and POSIX tools expect a trailing newline, and its absence can cause noisy diffs in future PRs.

Suggested change

	</ItemGroup>
	</Project>
	</ItemGroup>
	</Project>

Prompt To Fix With AI

This is a comment left during a code review.
Path: Directory.Packages.props
Line: 30-31

Comment:
The file no longer ends with a newline after this change. Most editors and POSIX tools expect a trailing newline, and its absence can cause noisy diffs in future PRs.

```suggestion
  </ItemGroup>
</Project>
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!