Skip to content

docs: v6.7.1 catch-up - #106

Draft
seidroid[bot] wants to merge 2 commits into
mainfrom
docs-bridge/release-v6.7.1
Draft

seidroid[bot] wants to merge 2 commits into
mainfrom
docs-bridge/release-v6.7.1

Conversation

@seidroid

@seidroid seidroid Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Documentation catch-up for v6.7.1.

2 source PR(s) produced changes across 2 commit(s). Each source PR is a separate commit, so this reviews commit-by-commit.

source PR pages touched summary
sei-protocol/sei-chain#4489 evm/installing-seid-cli.mdx The seid export command and its flags (--height, --for-zero-height, --jail-allowed-addrs, --streaming, --streaming-file) have been removed entirely, along with all module ExportGenesis functionality.
sei-protocol/sei-chain#4502 node/giga-storage-migration.mdx, node/troubleshooting.mdx FlatKV rollback and historical reads now refuse targets that cannot be reconstructed from retained history, returning an explicit error that advises using state sync instead, and stale idle FlatKV directories are now auto-discarded on startup.

⛔ Failed final verification against the release tag

Each touched page was re-checked claim-by-claim against the v6.7.1 checkout after all commits were assembled. The items below contradict what actually ships at the tag and must be resolved before merging.

  • node/troubleshooting.mdx (Sync performance issues → "Increase the packet payload size" TOML sample (config.toml [p2p] section)) — max-packet-msg-payload-size = 1024000 # Increase from default 102400 — states the default is 102400.
    • evidence: The shipped default comes from DefaultP2PConfig at sei-tendermint/config/config.go:807 (MaxPacketMsgPayloadSize: 1000000), rendered into config.toml via sei-tendermint/config/toml.go:391 (max-packet-msg-payload-size = {{ .P2P.MaxPacketMsgPayloadSize }}). The default is 1000000, not 102400. (The 102400 value only appears in static docker fixture configs docker/localnode/config/config.toml:241 and docker/rpcnode/config/config.toml:241, which are not the template default.)

Reviewer notes

  • Backport release/v6.7: Remove genesis export sei-chain#4489 — The dominant gap is the seid export command listing in evm/installing-seid-cli.mdx, which must be removed. The [genesis] config block in node/node-operators.mdx (auto-generated app.toml, between AUTO-GENERATED:APP_TOML markers) already describes stream-import/genesis-stream-file as import-only, so the GenesisConfig comment change is reflected automatically when the app.toml is regenerated; no manual prose edit is strictly required there. No existing docs page documents the removed --height, --for-zero-height, --jail-allowed-addrs, --streaming, or --streaming-file flags, nor module ExportGenesis internals, so no additional page needs updating for those. The migration note about mid-migration exports was internal code commentary (app/migration/params.go) and is not surfaced in docs. I flagged node/swagger.mdx tentatively but it does not actually cover export behavior; the reviewer may choose to drop it — the real actionable change is removing the export line from the CLI command overview.
  • Backport release/v6.7: Guard FlatKV rollback floor sei-chain#4502 — The changes are backend behavior in sei-db with no corresponding config flag or CLI command, so the documentation gap is purely explanatory (what error operators will see and the recommended recovery path of state sync). The ErrVersionUnreachable error and the discardStaleIdleFlatKV startup cleanup are internal implementation details; only the operator-visible consequences (refused rollback/reads, auto-discard of stale FlatKV dirs) warrant documentation. Judgment call: giga-storage-migration.mdx is the most relevant page for FlatKV-specific behavior, while troubleshooting.mdx is relevant for the rollback error an operator would encounter. No new page is needed.

⚠️ Possible contradictions or misplaced sections

Flagged by a review of every touched page's final text. Each source PR was analysed in isolation, so these were invisible to the per-PR checks. Verify before merging — the checker cannot tell which side of a contradiction is correct.

Analyzing the pages for the specified issue types:

  • export command contradiction (evm/installing-seid-cli.mdx): The diff removes the export Export state to JSON line from the command list, but the <Note> still says only compact, latest_version, and prune "were removed in v6.6.0" — the command overview output and removal note don't account for export being removed, though this is a diff-only removal with no textual contradiction. (No actual contradiction in final text — ignore.)

  • evm_migrated vs migrate_evm/steady-state naming (giga-storage-migration.mdx): The "Pinning a write mode" section says a node refuses to start if a pinned evm_migrated mode disagrees with disk state, and the write-modes table defines evm_migrated as "The steady state after the evm/ migration." These are consistent. (No contradiction.)

  • ss-backend / rs-backend value naming inconsistency (giga-storage-migration.mdx): The receipt-backend FAQ states supported values are pebbledb (also called pebble) and littidx, and that GIGA_STORAGE=true defaults RECEIPT_BACKEND to pebble. These are consistent (pebble = pebbledb). (No contradiction.)

  • Duplicated content across pages (giga-storage-migration.mdx and troubleshooting.mdx): The inserted "Rollback and historical reads below retained FlatKV history" section appears in both pages. This is redundancy, not a contradiction within a single page. (Not reportable under the criteria.)

After checking for direct contradictions, inconsistent identifier spellings, removed-yet-configurable settings, and misplaced insertions:

NONE


Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.

seidroid Bot added 2 commits November 14, 2026 06:29
…eight, --jail-allowed-addrs, --streaming, --streaming-file) have been removed entirely, along with all module ExportGenesis functionality. (sei-protocol/sei-chain#4489)
…nnot be reconstructed from retained history, returning an explicit error that advises using state sync instead, and stale idle FlatKV directories are now auto-discarded on startup. (sei-protocol/sei-chain#4502)
@seidroid seidroid Bot added the automated Automated PR from sei-docs-bridge label Nov 14, 2026
@mintlify

mintlify Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
sei-docs 🟢 Ready View Preview Nov 14, 2026, 6:33 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

This branch was successfully deployed

1 active deployment
staging — ce4422a8 Deployed Nov 14, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated PR from sei-docs-bridge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants