chore: changelog v1.2.1

[tac0turtle]

Renames the ## v1.2.0 changelog section to ## v1.2.1 and notes that v1.2.0 was superseded (it was tagged before core/v1.1.0 was published, so it required an unavailable core version and is unusable by consumers).

Why this matters

The GitHub Release workflow (release-github.yml) reads CHANGELOG.md from the checked-out ref (main — no ref: override), searching for a section matching the release version. Releasing tag v1.2.1 needs a ## v1.2.1 section or the notes come out empty.

Merge this before running the "Github Release" workflow for v1.2.1.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated the changelog to identify the current release as v1.2.1.
  • Clarified that v1.2.1 supersedes v1.2.0 and includes the listed changes.

[github-actions]

The latest Buf updates on your PR. Results from workflow CI / buf-check (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	✅ passed	⏩ skipped	Jul 20, 2026, 12:11 PM

[coderabbitai]

Warning

Review limit reached

@tac0turtle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e6705567-4007-4c0c-8754-f4553d6158f3

📥 Commits

Reviewing files that changed from the base of the PR and between 685ae5b and c214838.

📒 Files selected for processing (1)

• CHANGELOG.md

📝 Walkthrough

Walkthrough

The changelog’s current release heading changes from v1.2.0 to v1.2.1, with a note explaining that v1.2.1 supersedes v1.2.0 and contains the entries below.

Changes

Release documentation

Layer / File(s)	Summary
Update release block labeling CHANGELOG.md	The release heading changes to v1.2.1, with a note explaining the superseded v1.2.0 tag and the entries included in v1.2.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• evstack/ev-node#3390: Updates the v1.2.x release headings and sections in the same changelog.

Suggested reviewers: julienrbrt, chatton, auricom

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the changelog bump to v1.2.1.
Description check	✅ Passed	The description covers the change, rationale, and release workflow impact, though it does not use the template's Overview heading.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/changelog-1.2.1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.30%. Comparing base (8dc1619) to head (c214838).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3394   +/-   ##
=======================================
  Coverage   62.30%   62.30%           
=======================================
  Files         120      120           
  Lines       13454    13454           
=======================================
  Hits         8382     8382           
+ Misses       4130     4129    -1     
- Partials      942      943    +1     

Flag	Coverage Δ
combined	62.30% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.