Backport release/v6.7: Update v6.7 changelog in prep to cut rc4

[seidroid]

Backport of #4406 to release/v6.7.

[seidroid]

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-4406-to-release/v6.7
git worktree add --checkout .worktree/backport-4406-to-release/v6.7 backport-4406-to-release/v6.7
cd .worktree/backport-4406-to-release/v6.7
git reset --hard HEAD^
git cherry-pick -x 1d30aa159199b31af1dc10461839234cfbc05137
git push --force-with-lease

[cursor]

PR Summary

Low Risk
Documentation-only change with no runtime impact, but merging with conflict markers or without restoring upgrade-guide content would publish a broken or incomplete v6.7 release notes.

Overview
Release-notes-only backport (#4406) that reshapes the v6.7 section of CHANGELOG.md for cutting rc4.

It drops the former Improvements and Upgrade guide subsections (operator-facing summaries of WebSocket limits, query pagination caps, IBC/feegrant removal, legacy sei_* RPC removal, etc.) and switches to the flat sei-chain bullet list used elsewhere in the file.

The diff adds changelog lines for recent release/v6.7 backports (SeiDB/FlatKV migration fixes, eth_getLogs panic handling, migration pause/KV repair tooling, goreleaser timeout, rc2/rc3 version bumps, and related items).

Review blocker: the file still contains unresolved git conflict markers (<<<<<<<, =======, >>>>>>>) around the new bullets—the incoming side should be kept and markers removed before merge.

^{Reviewed by Cursor Bugbot for commit aa0bca6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[seidroid]

The automated review did not complete; see the failing AI Review check for details.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit aa0bca6. Configure here.}

[cursor]

Unresolved merge conflict in changelog

Medium Severity

Unresolved git conflict markers (<<<<<<< HEAD, =======, >>>>>>>) are committed in CHANGELOG.md. HEAD only has #4347, which is already on the incoming rc4 list, so the markers and the duplicate #4347 row would ship in the rc4 notes.

 

^{Reviewed by Cursor Bugbot for commit aa0bca6. Configure here.}

[github-actions]

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

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Oct 1, 2026, 5:49 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.45%. Comparing base (f30175a) to head (aa0bca6).
⚠️ Report is 1 commits behind head on release/v6.7.

Additional details and impacted files

@@               Coverage Diff                @@
##           release/v6.7    #4415      +/-   ##
================================================
- Coverage         61.48%   60.45%   -1.03%     
================================================
  Files              2168     2069      -99     
  Lines            189616   177872   -11744     
================================================
- Hits             116584   107540    -9044     
+ Misses            62251    60499    -1752     
+ Partials          10781     9833     -948     

Flag	Coverage Δ
sei-db	69.80% <ø> (ø)
sei-db-state-db	?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 99 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.