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

[seidroid]

Backport of #4110 to release/v6.7.

[seidroid]

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

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

[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	Sep 9, 2026, 6:03 PM

[cursor]

PR Summary

Low Risk
Changelog-only edit with no application or configuration behavior changes.

Overview
Prepares the v6.7 release notes in CHANGELOG.md by renaming the top section from Unreleased to v6.7 and appending a long sei-chain PR index (roughly #4095–#3425), including backports and the work already summarized under Improvements and Upgrade guide.

This is a documentation-only backport of changelog generation ahead of tagging release/v6.7; it does not change runtime code.

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

[seidroid]

Changelog-only backport that renames ## Unreleased to ## v6.7 and appends the full v6.7 PR list. Entries are well-formed (links match their PR numbers, strictly descending, no duplicates within the list); the only note is that the appended list has no heading, so it renders as part of the preceding ### Upgrade guide section.

Findings: 0 blocking | 2 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• None at the file/PR level.
• 1 suggestion(s)/nit(s) flagged inline on specific lines.
• 1 non-blocking pre-existing issue(s) listed below under pre-existing issues.

Pre-existing issues

• [suggestion] CHANGELOG.md:46 (unchanged context in this PR) tells clients they "can enable sei_getTransactionReceipt" for synthetic receipts, but that method is not in seiLegacyGatedMethods (evmrpc/sei_legacy.go:42, which only gates sei_getCosmosTx, sei_getEVMAddress, sei_getSeiAddress), so no [evm] enabled_legacy_sei_apis value can restore it. Following the migration advice cannot work.

Inline comments (could not post inline; listed here)

• CHANGELOG.md:48 (RIGHT) -- [suggestion] This bare sei-chain line and the ~280 entries under it are appended directly after the ### Upgrade guide section, so in rendered Markdown the whole PR list reads as content of the upgrade guide. In the ## v6.6 section (line 329) the same sei-chain list works because that release has no ### subsections above it. Either give this list its own heading (e.g. ### All changes) or move it above ### Improvements / ### Upgrade guide so the curated sections stay distinct from the generated list.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.30%. Comparing base (e693f65) to head (ca48a69).

Additional details and impacted files

@@               Coverage Diff                @@
##           release/v6.7    #4113      +/-   ##
================================================
- Coverage         61.34%   60.30%   -1.04%     
================================================
  Files              2163     2064      -99     
  Lines            188767   177084   -11683     
================================================
- Hits             115801   106798    -9003     
+ Misses            62247    60509    -1738     
+ Partials          10719     9777     -942     

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.

[alexander-sei]

@seidroid review

[seidroid]

Changelog-only backport that renames ## Unreleased to ## v6.7 and appends the generated v6.7 PR list; the entries are well-formed, strictly descending, duplicate-free, and correctly scoped to this release branch. The only note is the previously reported missing heading for the appended list, which the current revision still has.

Findings: 0 blocking | 2 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• None at the file/PR level.
• 1 suggestion(s)/nit(s) flagged inline on specific lines.
• 1 non-blocking pre-existing issue(s) listed below under pre-existing issues.

Pre-existing issues

• [suggestion] CHANGELOG.md:46 (unchanged context in this PR) tells clients they "can enable sei_getTransactionReceipt" for synthetic receipts, but that method is not in seiLegacyGatedMethods (evmrpc/sei_legacy.go:42, which gates only sei_getCosmosTx, sei_getEVMAddress, sei_getSeiAddress), so no [evm] enabled_legacy_sei_apis value can restore it. Following the migration advice cannot work.

Inline comments (could not post inline; listed here)

• CHANGELOG.md:48 (RIGHT) -- [suggestion] Re-raising: this bare sei-chain line and the 278 entries under it are appended directly after the ### Upgrade guide section, so in rendered Markdown the whole generated PR list reads as content of the upgrade guide. In the ## v6.6 section (line 328) the same sei-chain list works because that release has no ### subsections above it. Either give this list its own heading (e.g. ### All changes) or move it above ### Improvements / ### Upgrade guide so the curated sections stay distinct from the generated list.