Skip to content

Bump version to v6.7.0 in prep for release - #4444

Merged
masih merged 2 commits into
release/v6.7from
alex/v6-7-0-version
Oct 5, 2026
Merged

masih merged 2 commits into
release/v6.7from
alex/v6-7-0-version

Conversation

@alexander-sei

Copy link
Copy Markdown
Contributor

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, Bump version file in prep to cut v6.6 RC5 #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

  • git diff --check

Made with Cursor

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

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

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

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedOct 5, 2026, 9:45 AM

@codecov

codecov Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.68%. Comparing base (01ec2b0) to head (5094c4e).

Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##           release/v6.7    #4444      +/-   ##
================================================
- Coverage         61.70%   60.68%   -1.02%     
================================================
  Files              2171     2071     -100     
  Lines            189923   178070   -11853     
================================================
- Hits             117187   108058    -9129     
+ Misses            61860    60096    -1764     
+ Partials          10876     9916     -960     
Flag Coverage Δ
sei-db 70.02% <ø> (+0.21%) ⬆️
sei-db-state-db ?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 101 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
alexander-sei requested a review from masih October 5, 2026 09:25
@alexander-sei
alexander-sei marked this pull request as ready for review October 5, 2026 09:44

@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.

This PR changes one line: it bumps version.json from v6.7.0-rc4 to v6.7.0 for the final v6.7 release, matching the PR description. I found no issues.

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

Blockers

  • None at the file/PR level.

Non-blocking

  • None at the file/PR level.

@masih
masih merged commit 60dfac1 into release/v6.7 Oct 5, 2026
79 of 80 checks passed
@masih
masih deleted the alex/v6-7-0-version branch October 5, 2026 10:57
revofusion pushed a commit to revofusion/sei-chain that referenced this pull request Oct 5, 2026
Adds the `release/v6.7` entries merged since the rc4 changelog (sei-protocol#4406),
in prep to cut **v6.7.0**, the mainnet release (there is no rc5; the
version bump is sei-protocol#4444):

- [sei-protocol#4442](sei-protocol#4442) —
fix(seidb): fix stale FlatKV migration gauges on snapshotting nodes
- [sei-protocol#4439](sei-protocol#4439) — seidb:
add changelog mode and --inspect-plan to speed up EVM digest
- [sei-protocol#4416](sei-protocol#4416) — removal
of the conflict markers the rc4 changelog backport left on
`release/v6.7`
- [sei-protocol#4415](sei-protocol#4415) — rc4
changelog backport
- [sei-protocol#4407](sei-protocol#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>
masih pushed a commit that referenced this pull request Oct 8, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

non-app-hash-breaking release Tracks Release Branches

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants