Repository navigation
Update changelog in prep to cut v6.7 - #4110
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
![seidroid[bot]](https://avatars.githubusercontent.com/in/2745135?s=60&v=4){kind=small}
There was a problem hiding this comment.
Documentation-only PR that cuts a ## v6.7 section out of ## Unreleased and appends the generated PR list. I verified the split is internally consistent — the four PRs kept under ## Unreleased (#4009, #4021, #4032, #4078) do not appear in the v6.7 list, the v6.7 list has no duplicates within itself or against the v6.6 list, every PR referenced from the curated v6.7 subsections is present in the list, and the list is in descending order. Two non-blocking documentation issues remain.
Findings: 0 blocking | 3 non-blocking | 1 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- [suggestion] The new
## v6.7Upgrade guide omits client-breaking removals that the v6.7 PR list ships: #3912 (sei2_*API removal), #3926 (eth_getProofnow returnsErrEVMNotSupported, seeevmrpc/state.go:105), and #3945 (sei_getTransactionReceiptremoval). Since this PR is where the v6.7 release notes are finalized, these are worth an upgrade-guide entry rather than only a line in the generated PR list. - 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:60(the #3927 upgrade-guide entry, unchanged by this PR but now published under## v6.7) tells clients that "clients that know the synthetic transaction hash can enablesei_getTransactionReceipt". #3945 — listed in the same v6.7 section — removed that endpoint and its config option; no production implementation remains inevmrpc/. The advice cannot work on a v6.7 node and should point at v6.6 freeze nodes for historical synthetic receipts instead.
| * [#4009](https://github.com/sei-protocol/sei-chain/pull/4009) **`/store/*/subspace` scans are now capped.** Wide prefix scans that previously returned unbounded KV pairs now fail with `subspace result exceeds limit` once they would exceed the default caps of 1,000 pairs or 4 MiB of accumulated key+value bytes. Empty prefixes are rejected. Indexers and tooling that issue wide `/subspace` queries must narrow their prefixes, shard by sub-prefix, or raise `[state-commit] sc-subspace-max-pairs` and `sc-subspace-max-bytes` before upgrading. Values `<= 0` resolve to these defaults; there is no unlimited setting. | ||
| * [#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 |
There was a problem hiding this comment.
[suggestion] The bare sei-chain line works under ## v6.6 because that section has no subsections, but here it lands after ### Upgrade guide, so the ~180-entry generated PR list renders as part of the upgrade guide. A reader scanning the v6.7 upgrade instructions gets the full commit log appended to them. Give the list its own heading (e.g. ### All changes) or move it above ### Improvements.
masih
approved these changes
Sep 9, 2026
|
Created backport PR for
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 |
alexander-sei
added a commit
that referenced
this pull request
Sep 9, 2026
Systematic changelog re-generation in prep to cut the v6.7 release. Co-authored-by: Cursor <cursoragent@cursor.com> (cherry picked from commit a665891)
alexander-sei
added a commit
that referenced
this pull request
Sep 9, 2026
Backport of #4110 to `release/v6.7`. Co-authored-by: alexander-sei <alexanderh@seinetwork.io> Co-authored-by: Cursor <cursoragent@cursor.com>
masih
pushed a commit
that referenced
this pull request
Sep 22, 2026
Adds the `release/v6.7` entries merged since the rc1 changelog (#4110), in prep to cut **v6.7.0-rc2**: - [#4292](#4292) — Flush MemIAVL changelog before exiting on an upgrade panic - [#4285](#4285) — fix(seidb): refuse a corrupted changelog in digest replay instead of repairing it - [#4255](#4255) — feat(seidb): Add JSON output to evm-logical-digest and inspect a FlatKV migration in flight - [#4116](#4116) — rc1 version bump - [#4113](#4113) — rc1 changelog backport Regenerated with `./scripts/generate-changelog.sh release/v6.6 release/v6.7`; only the `## v6.7` PR list changes, so the `backport release/v6.7` cherry-pick applies cleanly (verified with `git apply --check` against `origin/release/v6.7`). Docs-only; no code change. Made with [Cursor](https://cursor.com) Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Systematic changelog re-generation in prep to cut the v6.7 release.