Title the changelog section for release 4.0.13

[davidnmbond]

Retitles the changelog's Unreleased section now that 4.0.13 is published.

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation (-1.00%)
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (9de87d5)	206	135	65.53%
Head commit (b302b17)	206 (+0)	135 (+0)	65.53% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#50)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

While this PR correctly identifies the need to title the current release section, the version number 4.0.13 is inappropriate for the changes described. The changelog documents breaking changes (e.g., API removals and return type modifications) and significant feature additions (170+ operations), which requires a Major or Minor version bump according to the Semantic Versioning rules specified in the file.

Additionally, the update violates the 'Keep a Changelog' standard by omitting a release date and failing to initialize a new 'Unreleased' section for future contributions. These issues should be addressed before merging to maintain versioning integrity.

About this PR

• When marking a release in the changelog, a new '## Unreleased' section should be initialized at the top of the file to capture future changes immediately after the release.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🔴 HIGH RISK}

This release introduces breaking changes (such as the removal of CleanCacheAsync and changing method return types to Stream) along with extensive new functionality (170+ operations). Per the Semantic Versioning specification referenced on line 6, these changes require a MAJOR version bump (5.0.0) or at minimum a MINOR bump (4.1.0) rather than a PATCH bump (4.0.13). Additionally, to comply with the 'Keep a Changelog' standard referenced on line 5, the header should include the release date in YYYY-MM-DD format.