Repository navigation
Update v6.7 changelog in prep to cut v6.7.0 - #4443
Conversation
Adds the release/v6.7 entries merged since the rc4 changelog (#4406): #4442, #4439, the conflict-marker fix (#4416), the rc4 changelog backport (#4415), and the rc4 version bump (#4407). Regenerated with ./scripts/generate-changelog.sh release/v6.6 release/v6.7. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
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
masih
left a comment
There was a problem hiding this comment.
LGTM, but the PR title is inaccurate.
@alexander-sei we are going to cut v6.7 -- not anohter release candidate ;)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4443 +/- ##
==========================================
- Coverage 56.75% 54.98% -1.77%
==========================================
Files 2126 2003 -123
Lines 166836 154474 -12362
==========================================
- Hits 94691 84944 -9747
+ Misses 72140 69525 -2615
Partials 5 5
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Successfully created backport PR for |
## Summary - Bump `version.json` from `v6.7.0-rc4` to `v6.7.0` to cut the final `v6.7` release for mainnet. There is no rc5: this goes straight from rc4 to the release. (v6.6.0 was tagged on the rc5 bump, #3783, with `version.json` still reading `v6.6.0-rc5`; this keeps `version.json` in step with the tag.) Contents since rc4: #4442 and #4439, plus the changelog update (#4443). Merge this after #4443's backport has landed on `release/v6.7`, so the `v6.7.0` tag includes the updated changelog. - Both are labeled `non-app-hash-breaking` (a FlatKV migration metrics fix and `seidb` digest tooling), so moving from rc4 to `v6.7.0` should not need a coordinated validator switch. - Push `v6.7.0` by hand on this PR's merge commit once it has merged; the tagging ruleset stops `uci-release-publish` from creating it. ## Test plan - [x] `git diff --check` Made with [Cursor](https://cursor.com) Co-authored-by: Cursor <cursoragent@cursor.com>
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>
Adds the
release/v6.7entries 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):release/v6.7Regenerated with
./scripts/generate-changelog.sh release/v6.6 release/v6.7; only the## v6.7PR list changes, so thebackport release/v6.7cherry-pick applies cleanly (simulated withgit merge-treeagainstorigin/release/v6.7). Docs-only; no code change.Made with Cursor