Skip to content

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

Closed
alexander-sei wants to merge 1 commit into
release/v6.7from
alex/v6-7-changelog-release
Closed

alexander-sei wants to merge 1 commit into
release/v6.7from
alex/v6-7-changelog-release

Conversation

@alexander-sei

Copy link
Copy Markdown
Contributor

Backport of #4110 to release/v6.7.

Opened by hand rather than via the backport label: the ## Unreleased hunk in #4110 does not cherry-pick cleanly onto release/v6.7, which lacks the main-only entries (#4009, #4032, #4021, #4078) that stay under ## Unreleased there.

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

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

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedSep 9, 2026, 5:39 PM

@seidroid seidroid Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CHANGELOG-only backport that renames ## Unreleased to ## v6.7 and appends the full v6.7 merge list; the main-only entries (#4009, #4032, #4021, #4078) are correctly excluded and I confirmed none of those features are present on this branch. One non-blocking structural note about where the flat list is inserted, plus one pre-existing inaccuracy in unchanged text.

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, also present on main): the #3927 upgrade-guide entry tells clients that "clients that know the synthetic transaction hash can enable sei_getTransactionReceipt", but the sei namespace in evmrpc/server.go:167-170 now registers only AssociationAPI, so no sei_getTransactionReceipt method is reachable (its removal is itself listed in this release via #3945). The guidance points operators at an endpoint that cannot be enabled.

Comment thread CHANGELOG.md
* [#3984](https://github.com/sei-protocol/sei-chain/pull/3984) **ABCI/gRPC pagination is now capped by default.** Untrusted callers requesting `limit` above 1000, `offset` above 10000, or a scan that exceeds 11000 total iterations now get `InvalidArgument` (over-cap) or a partial page with `next_key` (budget exhausted) instead of the previously unbounded scan. Clients that page with large limits/offsets, or trusted internal indexers, should either follow `next_key` for resumption or be added to the new `[query] trusted-cidrs` allowlist (or set `[query] disable-limits = true`) before upgrading.
* [#3927](https://github.com/sei-protocol/sei-chain/pull/3927) **Legacy Sei JSON-RPC and CLI removal.** Removes `sei_associate`, `sei_getBlockByHash`, `sei_getBlockByHashExcludeTraceFail`, `sei_getBlockTransactionCountByHash`, `sei_getBlockTransactionCountByNumber`, `sei_getEvmTx`, `sei_getFilterChanges`, `sei_getFilterLogs`, `sei_getLogs`, `sei_getTransactionByBlockHashAndIndex`, `sei_getTransactionByBlockNumberAndIndex`, `sei_getTransactionByHash`, `sei_getTransactionCount`, `sei_getTransactionErrorByHash`, `sei_getTransactionReceiptExcludeTraceFail`, `sei_getVMError`, `sei_newBlockFilter`, `sei_newFilter`, `sei_sign`, and `sei_uninstallFilter`. Use standard `eth_*` methods for EVM-originated data and `seid tx evm native-associate <custom-message> -y` for address association. There is no block- or filter-level replacement for discovering Cosmos-originated synthetic logs; clients that know the synthetic transaction hash can enable `sei_getTransactionReceipt`.

sei-chain

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] The sei-chain list is appended after ### Upgrade guide, so ~280 raw merge entries render as a continuation of the upgrade guide rather than as the release's commit log. Every other version section in this file (## v6.6, ## v6.5, …) puts sei-chain immediately under the version heading, before any subsection. Moving this block to just after ## v6.7 (line 31) would keep the operationally important ### Upgrade guide as the last thing in the section and match the existing convention.

Non-blocking, and I recognize this mirrors the already-merged #4110 exactly — flagging it so the two can be fixed together rather than asking this backport to diverge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant