Skip to content

Update v6.7 changelog in prep to cut rc3 - #4335

Closed
alexander-sei wants to merge 6 commits into
mainfrom
alex/v6-7-changelog-rc3
Closed

alexander-sei wants to merge 6 commits into
mainfrom
alex/v6-7-changelog-rc3

Conversation

@alexander-sei

@alexander-sei alexander-sei commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Adds the release/v6.7 entries merged since the rc2 changelog (#4293), in prep to cut v6.7.0-rc3:

  • #4348 — fix(seidb): report only the current migration boundary on the snapshot gauge
  • #4347 — fix(flatkv): keep 10 old checkpoints instead of mirroring memIAVL's count
  • #4334 — Fail dynamic-gas precompile out-of-gas as an EVM out-of-gas call
  • #4315 — Pin the Go builder image per architecture in build-static.sh
  • #4313 — fix(memiavl): hold a snapshot reference for an iterator's lifetime
  • #4295 — rc2 version bump
  • #4294 — rc2 changelog backport

Also returns ## v6.7 to the format used through v6.6: the version heading, sei-chain, and the generated PR list. The hand-written ### Improvements and ### Upgrade guide sections are removed; every PR they described is already a line in the generated list.

Regenerated with ./scripts/generate-changelog.sh release/v6.6 release/v6.7; only the ## v6.7 section changes. Docs-only; no code change.

Backport note: the #4347 backport already added its own line to the top of the ## v6.7 list on release/v6.7, so the backport release/v6.7 cherry-pick of this PR conflicts at that one spot (simulated with git merge-tree). Resolve it by taking this PR's side: its seven lines already include #4347.

Adds the release/v6.7 entries merged since the rc2 changelog (#4293),
in prep to cut v6.7.0-rc3: #4334, #4315, #4313, the rc2 version bump
(#4295), and the rc2 changelog backport (#4294).

Regenerated with ./scripts/generate-changelog.sh release/v6.6 release/v6.7.

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

github-actions Bot commented Sep 25, 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 25, 2026, 8:27 PM

@codecov

codecov Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.43%. Comparing base (3a61e67) to head (9e71338).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #4335      +/-   ##
==========================================
- Coverage   67.55%   66.43%   -1.13%     
==========================================
  Files        2162     2041     -121     
  Lines      167529   155445   -12084     
==========================================
- Hits       113182   103273    -9909     
+ Misses      54338    52163    -2175     
  Partials        9        9              
Flag Coverage Δ
sei-db 74.50% <ø> (ø)
sei-db-state-db ?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 121 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 and others added 2 commits September 25, 2026 13:49
Removes the hand-written ## Unreleased section and the ### Improvements
and ### Upgrade guide sections under ## v6.7, so each release is again
its version heading, sei-chain, and the list printed by
scripts/generate-changelog.sh.

Co-authored-by: Cursor <cursoragent@cursor.com>
release/v6.7 has no Unreleased section, so changing it here would make
the backport conflict. The Unreleased list is regenerated in a separate
main-only change instead.

Co-authored-by: Cursor <cursoragent@cursor.com>
revofusion pushed a commit to revofusion/sei-chain that referenced this pull request Sep 25, 2026
…4336)

Replaces the hand-written `## Unreleased` section with the generated PR
list, in the format every released version uses: the heading,
`sei-chain`, and one line per PR.

Generated with `./scripts/generate-changelog.sh release/v6.7 main` (175
PRs merged to `main` since `release/v6.7` branched), with the script's
`## main` heading renamed to `## Unreleased`. The eight PRs that had
hand-written entries (sei-protocol#4166, sei-protocol#4098, sei-protocol#4191, sei-protocol#4117, sei-protocol#4078, sei-protocol#4032, sei-protocol#4021,
sei-protocol#4009) are all in the list.

`main` only, so no backport label: `release/v6.7` has no Unreleased
section, and cherry-picking this there conflicts. It is independent of
sei-protocol#4335, which touches only `## v6.7`; the two merge cleanly in either
order. Docs-only; no code change.

Made with [Cursor](https://cursor.com)

Co-authored-by: Cursor <cursoragent@cursor.com>
alexander-sei and others added 3 commits September 25, 2026 21:51
Regenerated with ./scripts/generate-changelog.sh release/v6.6 release/v6.7.

Co-authored-by: Cursor <cursoragent@cursor.com>
Regenerated with ./scripts/generate-changelog.sh release/v6.6 release/v6.7.

Co-authored-by: Cursor <cursoragent@cursor.com>
@masih
masih marked this pull request as ready for review September 25, 2026 20:26
@cursor

cursor Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Only CHANGELOG.md is edited; release notes formatting with no code or configuration impact.

Overview
Prepares v6.7.0-rc3 by regenerating the ## v6.7 block in CHANGELOG.md with ./scripts/generate-changelog.sh release/v6.6 release/v6.7.

The section now matches the v6.6-style layout (sei-chain plus an auto-generated PR list). Seven entries are prepended for work merged on release/v6.7 since the rc2 changelog (#4294), including seidb snapshot-gauge reporting, flatkv checkpoint retention, dynamic-gas precompile OOG behavior, memiavl iterator snapshot refs, and the rc2 version/changelog bumps.

The hand-written ### Improvements and ### Upgrade guide subsections are removed; those topics remain discoverable as individual lines in the generated list. Documentation only—no runtime or build behavior changes.

Reviewed by Cursor Bugbot for commit 9e71338. Bugbot is set up for automated code reviews on this repo. Configure here.

@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 only changes the changelog. The new rc3 entries match the PR list and follow the v6.6 format. However, it deletes the v6.7 upgrade guide, which holds operator migration steps that appear nowhere else in the repo's docs.

Findings: 0 blocking | 1 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.

Comment thread CHANGELOG.md
* [#3984](https://github.com/sei-protocol/sei-chain/pull/3984) feat(query): origin-aware pagination limits for ABCI queries. Untrusted callers on the ABCI/gRPC query path get configurable `max-limit`, `max-offset`, and flat `max-iterations` (defaults: 1000 / 10000 / 11000); requests above the caps are rejected upfront, and an exhausted iteration budget returns a partial page with `next_key` instead of failing. Trusted origins (new `[query] trusted-cidrs`) and the `[query] disable-limits` kill switch bypass the caps; the consensus/EVM precompile path is unaffected.
* [#3990](https://github.com/sei-protocol/sei-chain/pull/3990) Freeze mode is limited to full nodes and disables transaction and evidence submission, mempool gossip, and state sync from startup while preserving query RPC and mempool-backed reads. Frozen and Autobahn nodes no longer advertise the unused mempool P2P channel.

### Upgrade guide

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 description says every PR this ### Upgrade guide described is already a line in the generated list. That doesn't hold. The generated PR titles keep none of the guidance operators need to act on:

  • The WebSocket frame limit default drops from 10 MiB to 5 MiB. Operators who need the old limit must set max_request_body_bytes = 10485760.
  • ABCI/gRPC pagination is now capped by default, with [query] trusted-cidrs and disable-limits as ways around the caps.
  • The legacy sei_* RPC methods are removed, and the guide listed their replacements.
  • Historical IBC, transfer and feegrant data must now be served by v6.6 freeze nodes.

The IBC core, IBC query and capability-removal items had no PR number at all. Nothing else in the repo's markdown carries this guidance. Without it, clients sending 5–10 MiB WebSocket frames and indexers that page with large limits can break without warning after the upgrade. Keep this section, or move it to an upgrade/migration doc and link to it from ## v6.7. Codex raised the same point.

@alexander-sei
alexander-sei requested a review from masih September 25, 2026 20:32
masih added a commit that referenced this pull request Sep 25, 2026
## Summary
- Bump `version.json` from `v6.7.0-rc2` to `v6.7.0-rc3` to cut the third
`v6.7` release candidate.

Contents since rc2: #4334, #4315, #4313, plus the rc3 changelog update
(#4335, via its `release/v6.7` backport). Merge after that backport so
the `v6.7.0-rc3` tag includes the updated changelog.

- #4334 (backport of #4318) is `app-hash-breaking` with no height gate,
so a network that already ran the v6.7 upgrade on rc1 or rc2 has to move
all of its validators to rc3 together.
- As on rc1 and rc2, the tagging ruleset stops `uci-release-publish`
from creating the tag on merge, so push `v6.7.0-rc3` on the merge commit
by hand; that push publishes the release and runs GoReleaser.
- #4315 fixes the arm64 static build that failed GoReleaser on the rc1
and rc2 tag pushes, so rc3 should be the first `v6.7` release candidate
with binaries attached.

## Test plan
- [x] `git diff --check`

Made with [Cursor](https://cursor.com)

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Masih H. Derkani <m@derkani.org>
masih pushed a commit that referenced this pull request Oct 1, 2026
Adds the `release/v6.7` entries merged since the rc2 changelog (#4293),
in prep to cut **v6.7.0-rc4**. The rc3 update (#4335) was closed without
merging, so its entries are included here:

- [#4411](#4411) — Log a
pinned node's skipped migration kick-off once per batch size
- [#4410](#4410) — Apply
compiled KV repair files at a fixed height and generate them from digest
inspect lists
- [#4409](#4409) — feat:
add migration pause handler
- [#4397](#4397) —
fix(evmrpc): release eth_getLogs DB-read slots when a block read panics
- [#4378](#4378) — Raise
goreleaser timeout to 2h
- [#4377](#4377) — Fix
FlatKV state sync bad-hash scenario
- [#4371](#4371) —
fix(seidb): keep writes in the old DB until the migration boundary first
moves
- [#4348](#4348) —
fix(seidb): report only the current migration boundary on the snapshot
gauge
- [#4347](#4347) —
fix(flatkv): keep 10 old checkpoints instead of mirroring memIAVL's
count
- [#4339](#4339) — rc3
version bump
- [#4334](#4334) — Fail
dynamic-gas precompile out-of-gas as an EVM out-of-gas call
- [#4315](#4315) — Pin the
Go builder image per architecture in build-static.sh
- [#4313](#4313) —
fix(memiavl): hold a snapshot reference for an iterator's lifetime
- [#4295](#4295) — rc2
version bump
- [#4294](#4294) — rc2
changelog backport

Also returns `## v6.7` to the format used through v6.6: the version
heading, `sei-chain`, and the generated PR list. The hand-written `###
Improvements` and `### Upgrade guide` sections are removed; every PR
they described is already a line in the generated list.

Regenerated with `./scripts/generate-changelog.sh release/v6.6
release/v6.7`; only the `## v6.7` section changes. Docs-only; no code
change.

**Backport note:** the #4347 backport added its own line to the top of
the `## v6.7` list on `release/v6.7`, and `main` doesn't have it, so the
`backport release/v6.7` cherry-pick of this PR conflicts at that one
spot (simulated with `git merge-tree`). Resolve it by taking this PR's
side: its fifteen lines already include #4347.

---------

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants