Skip to content

docs(run-a-node): bump blockchain_module to 0.3.2 - #564

Merged
kashepavadan merged 1 commit into
mainfrom
docs/blockchain-module-0.3.2
Oct 14, 2026
Merged

kashepavadan merged 1 commit into
mainfrom
docs/blockchain-module-0.3.2

Conversation

@davidrusu

Copy link
Copy Markdown
Contributor

Bumps the node operator guide (run-logos-node-blockchain-storage-delivery.md) from blockchain_module 0.3.1 to 0.3.2. The CLI and Basecamp blockchain guides were already moved to 0.3.2 in #562/#563.

Changes

  • Install command: --version 0.3.2 with the catalogue root hash 9ab4acbb…f0d7. This was checked with logosctl package search blockchain_module after a catalogue refresh, and the old 0.3.1 hash on the page matched the catalogue too.
  • Expected package ls output now shows blockchain_module 0.3.2.
  • Genesis warning: 0.3.2 runs on the same chain that 0.3.1 started, so only nodes coming from a release before 0.3.1 need an empty state directory. Nodes upgrading from 0.3.1 keep their state.

Verified against upstream (logos-blockchain 0.3.1...0.3.2)

  • Bootstrap peers in the 0.3.2 release notes are unchanged, so peers.json stays as it is.
  • No genesis or HTTP API changes. The release adds openmetrics over FFI, sets the gossipsub duplicate cache to 24h and recovers from lagged streams. That is why blockchain-api-reference.md stays pinned to node 0.3.1.
  • The metrics tracing config changed shape (an otlp / enable_open_metrics struct instead of an enum), but no page documents it.

Not changed

  • build-and-run-logos-blockchain-node-app-ui.md describes the blockchain_ui 0.3.1 branch, whose flake.lock pins module 0.3.0. It will change when the UI release changes.

Checks

  • npm run build passes.
  • vale reports no errors on the changed file.

🤖 Generated with Claude Code

@kashepavadan
kashepavadan merged commit 0f170f0 into main Oct 14, 2026
3 checks passed
@kashepavadan
kashepavadan deleted the docs/blockchain-module-0.3.2 branch October 14, 2026 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants