Repository navigation
Backport release/v6.7: Update v6.7 changelog in prep to cut v6.7.0 - #4445
Conversation
Adds the `release/v6.7` entries merged since the rc4 changelog (#4406), in prep to cut **v6.7.0**, the mainnet release (there is no rc5; the version bump is #4444): - [#4442](#4442) — fix(seidb): fix stale FlatKV migration gauges on snapshotting nodes - [#4439](#4439) — seidb: add changelog mode and --inspect-plan to speed up EVM digest - [#4416](#4416) — removal of the conflict markers the rc4 changelog backport left on `release/v6.7` - [#4415](#4415) — rc4 changelog backport - [#4407](#4407) — rc4 version bump 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 (simulated with `git merge-tree` against `origin/release/v6.7`). Docs-only; no code change. Made with [Cursor](https://cursor.com) Co-authored-by: Cursor <cursoragent@cursor.com> (cherry picked from commit 1d8e5f7)
|
@seidroid review |
PR SummaryLow Risk Overview The new bullets record recent release/v6.7 backports (FlatKV migration gauge fix on snapshotting nodes, seidb changelog mode and Reviewed by Cursor Bugbot for commit 61423e2. Bugbot is set up for automated code reviews on this repo. Configure here. |
![seidroid[bot]](https://avatars.githubusercontent.com/in/2745135?s=60&v=4){kind=small}
There was a problem hiding this comment.
Settled by the scouts (codex) without a review turn: every one of them read the diff, found nothing, and reported it inert -- comments, documentation or whitespace only, with no executable surface changed.
seidroid review · decision approve · settled by the scouts codex · no review turn ran
Findings: 0 blocking | 0 non-blocking | 0 posted inline
There was a problem hiding this comment.
This PR only changes the docs: it adds five v6.7 changelog entries (#4442, #4439, #4416, #4415, #4407). Each entry appears once, the file has no conflict markers, and the entries match the existing format and order.
Findings: 0 blocking | 0 non-blocking | 0 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- None at the file/PR level.
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/v6.7 #4445 +/- ##
================================================
- Coverage 61.69% 60.68% -1.02%
================================================
Files 2171 2071 -100
Lines 189923 178070 -11853
================================================
- Hits 117181 108057 -9124
+ Misses 61863 60097 -1766
+ Partials 10879 9916 -963
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Systematic changelog re-generation for the v6.7.1 patch release. Adds the PRs merged to `release/v6.7` since the v6.7.0 changelog (#4443), as reported by `scripts/generate-changelog.sh release/v6.6 release/v6.7`: - #4473 Backport `release/v6.7`: Make the composite store router an atomic pointer - #4465 Backport `release/v6.7`: fix(seidb): keep the memIAVL nonce when state sync restores a mid-mig… - #4445 Backport `release/v6.7`: Update v6.7 changelog in prep to cut v6.7.0 - #4444 Bump version to v6.7.0 in prep for release Only the `## v6.7` PR list changes, so the `backport release/v6.7` cherry-pick applies cleanly (simulated with `git merge-tree` against `origin/release/v6.7`). Not included: #4474 (the `release/v6.7` backport of #4469), which is still open. If it lands before the cut, this list needs regenerating. Co-authored-by: Cursor <cursoragent@cursor.com>
2 participants
Backport of #4443 to
release/v6.7.