chore(release): v0.13.10

[github-actions]

Cut CMakeLists, changelog, and install pins to v0.13.10. Squash-merge and keep this title; the version workflow then tags v0.13.10 and publishes binaries. main requires pull requests, so the bot cannot push this commit directly.

Confidence Score: 4/5

The release appears safe to merge operationally, but its non-blocking changelog accuracy issue should be corrected so v0.13.10 does not claim fixes already released in earlier versions.

Summary

This automated release PR advances Arbiter’s CMake version and public install/download pins to v0.13.10, then cuts the current Unreleased changelog content into a dated release section.

• The CMake, documentation, and website version pins are internally consistent.
• The release workflow and artifact naming align with the new version.
• The changelog cut incorrectly republishes numerous fixes already attributed to earlier releases.

_{Reviews (1) · Last reviewed commit: "chore(release): v0.13.10"}

[greptile-apps]

Duplicate release notes

The new 0.13.10 section includes many fixes already listed under earlier releases. For example, “Event ingest hydrates the routed constitution” and “Conversation list cursor” also appear under 0.13.9, while only three implementation commits landed after that release. Publishing this section as-is overstates the contents of 0.13.10 and makes the release history unreliable. Remove the previously released entries before publishing it.

Prompt To Fix With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 10

Comment:
**Duplicate release notes**

The new 0.13.10 section includes many fixes already listed under earlier releases. For example, “Event ingest hydrates the routed constitution” and “Conversation list cursor” also appear under 0.13.9, while only three implementation commits landed after that release. Publishing this section as-is overstates the contents of 0.13.10 and makes the release history unreliable. Remove the previously released entries before publishing it.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.