NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1863 by repository stars
Latest stable
v0.36.0
Last release 3 days ago
19 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
1265 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
⚠️ Note: this release requires a config update and - for BN runners - a migration step. ⚠️ See docs for further information.
⚠️ Note: this release requires a config update and - for BN runners - a migration step. ⚠️ See docs for further information.
⚠️ BRIDGE NODE RUNNERS MUST COMPLETE A MIGRATION STEP BEFORE UPGRADING ⚠️
In order to use header pruning, please check out the new header configuration parameters in config.toml:
[Header.Syncer]
# PruningWindow defines the duration within which headers are retained before being pruned.
# Default is 337 hours.
PruningWindow = "337h0m0s"
# SyncFromHash is the hash of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHash overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHash has higher priority than SyncFromHeight.
SyncFromHash = ""
# SyncFromHeight is the height of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHeight overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHeight has lower priority than SyncFromHash.
SyncFromHeight = 0
Please do not copy these values directly into the config -- please use the config-update command. Read the docs here.
Please do the following to migrate properly:
make cel-shed
./cel-shed header store-reset <node_path> --tail 1.
⚠️ This should happen before the new version binary is started, and must happen when the old binary is not running.
By default, node maintains a sliding window of headers, bounded by Tail and Head headers. Requests with height below the Tail are rejected (This is, however, temporary, and lazy header fetching will be available with Backward Sync)
To retain the ability to request older queries with LNs, use new configuration fields to set an absolute header that the node will sync from, either the SyncFromHeight or the SyncFromHash field.
Pruning for Bridge and Full nodes is disabled. Currently, the p2p protocol for headers cannot distinguish between pruned and non-pruned serving node types. Therefore, to keep stable synchronization of historical headers, we disable pruned servers.
StartTimeout value in the config, as LN prunes on start. If the starting times out, e.g., with the default 20s, the node will attempt to persist the progress, but storage state corruptions may still occur. The complete mainnet header history pruning on moderate hardware takes under 100s, so update your config accordingly.StartTimeout value in the config, as LN syncs the difference during start. (This is, however, temporary, and asynchronous syncing that doesn't block start will be available with Backward Sync).
Daser.SampleFrom field is no longer supported. Use Header.Syncer.SyncFromHeight instead.Header.TrustedHash field is no longer supported. Use Header.Syncer.SyncFromHash instead.Header.TrustedPeriod field was removed and is now a network-level constant.Replace for go-datastore was added, which may break users depending directly on the node's go.mod.
Do the following in your project's root to fix:
go mod edit -replace github.com/ipfs/go-datastore=github.com/celestiaorg/go-datastore@48a63ae && go mod tidy. It's gonna be removed in future releases.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.3...v0.26.4
Nothing published for this version
This release fixes a stream leak found by a few downstream users in the shrex client.
This release fixes a stream leak found by a few downstream users in the shrex client.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.26.3-mocha...v0.26.4-mocha
Contains a bump to celestia-app that should resolve account sequence mismatch errors
Contains a bump to celestia-app that should resolve account sequence mismatch errors
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.26.2-mocha...v0.26.3-mocha
Nothing published for this version
⚠️ Note: this release requires a config update and - for BN runners - a migration step. ⚠️ See docs for further information.
⚠️ Note: this release requires a config update and - for BN runners - a migration step. ⚠️ See docs for further information.
In order to use header pruning, please check out the new header configuration parameters in config.toml:
[Header.Syncer]
# PruningWindow defines the duration within which headers are retained before being pruned.
# Default is 337 hours.
PruningWindow = "337h0m0s"
# SyncFromHash is the hash of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHash overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHash has higher priority than SyncFromHeight.
SyncFromHash = ""
# SyncFromHeight is the height of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHeight overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHeight has lower priority than SyncFromHash.
SyncFromHeight = 0
Please do not copy these values directly into the config -- please use the config-update command. Read the docs here.
Please do the following to migrate properly:
make cel-shed
./cel-shed header store-reset <node_path> --tail 1.
⚠️ This should happen before the new version binary is started, and must happen when the old binary is not running.
By default, node maintains a sliding window of headers, bounded by Tail and Head headers. Requests with height below the Tail are rejected (This is, however, temporary, and lazy header fetching will be available with Backward Sync)
To retain the ability to request older queries with LNs, use new configuration fields to set an absolute header that the node will sync from, either the SyncFromHeight or the SyncFromHash field.
Pruning for Bridge and Full nodes is disabled. Currently, the p2p protocol for headers cannot distinguish between pruned and non-pruned serving node types. Therefore, to keep stable synchronization of historical headers, we disable pruned servers.
StartTimeout value in the config, as LN prunes on start. If the starting times out, e.g., with the default 20s, the node will attempt to persist the progress, but storage state corruptions may still occur. The complete mainnet header history pruning on moderate hardware takes under 100s, so update your config accordingly.StartTimeout value in the config, as LN syncs the difference during start. (This is, however, temporary, and asynchronous syncing that doesn't block start will be available with Backward Sync).
Daser.SampleFrom field is no longer supported. Use Header.Syncer.SyncFromHeight instead.Header.TrustedHash field is no longer supported. Use Header.Syncer.SyncFromHash instead.Header.TrustedPeriod field was removed and is now a network-level constant.Replace for go-datastore was added, which may break users depending directly on the node's go.mod.
Do the following in your project's root to fix:
go mod edit -replace github.com/ipfs/go-datastore=github.com/celestiaorg/go-datastore@48a63ae && go mod tidy. It's gonna be removed in future releases.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.26.1-mocha...v0.26.2-mocha
Nothing published for this version
⚠️ Note: this release requires a config update. ⚠️ See docs for further information.
⚠️ Note: this release requires a config update. ⚠️ See docs for further information.
In order to use header pruning, please check out the new header configuration parameters in config.toml:
[Header.Syncer]
# PruningWindow defines the duration within which headers are retained before being pruned.
# Default is 337 hours.
PruningWindow = "337h0m0s"
# SyncFromHash is the hash of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHash overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHash has higher priority than SyncFromHeight.
SyncFromHash = ""
# SyncFromHeight is the height of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHeight overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHeight has lower priority than SyncFromHash.
SyncFromHeight = 0
Please do not copy these values directly into the config -- please use the config-update command. Read the docs here.
By default, node maintains a sliding window of headers, bounded by Tail and Head headers. Requests with height below the Tail are rejected (This is, however, temporary, and lazy header fetching will be available with Backward Sync)
To retain the ability to request older queries with LNs, use new configuration fields to set an absolute header that the node will sync from, either the SyncFromHeight or the SyncFromHash field.
Pruning for Bridge and Full nodes is disabled. Currently, the p2p protocol for headers cannot distinguish between pruned and non-pruned serving node types. Therefore, to keep stable synchronization of historical headers, we disable pruned servers.
StartTimeout value in the config, as LN prunes on start. If the starting times out, e.g., with the default 20s, the node will attempt to persist the progress, but storage state corruptions may still occur. The complete mainnet header history pruning on moderate hardware takes under 100s, so update your config accordingly.StartTimeout value in the config, as LN syncs the difference during start. (This is, however, temporary, and asynchronous syncing that doesn't block start will be available with Backward Sync).
Daser.SampleFrom field is no longer supported. Use Header.Syncer.SyncFromHeight instead.Header.TrustedHash field is no longer supported. Use Header.Syncer.SyncFromHash instead.Header.TrustedPeriod field was removed and is now a network-level constant.Replace for go-datastore was added, which may break users depending directly on the node's go.mod.
Do the following in your project's root to fix:
go mod edit -replace github.com/ipfs/go-datastore=github.com/celestiaorg/go-datastore@48a63ae && go mod tidy. It's gonna be removed in future releases.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.3-mocha...v0.26.1-mocha
Nothing published for this version
⚠️ Note: this release requires a config update. ⚠️ See docs for further information.
⚠️ Note: this release requires a config update. ⚠️ See docs for further information.
In order to use header pruning, please check out the new header configuration parameters in config.toml:
[Header.Syncer]
# PruningWindow defines the duration within which headers are retained before being pruned.
# Default is 337 hours.
PruningWindow = "337h0m0s"
# SyncFromHash is the hash of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHash overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHash has higher priority than SyncFromHeight.
SyncFromHash = ""
# SyncFromHeight is the height of the header from which the syncer should start syncing.
# Zero value to disable. Value updates up and down the chain are gracefully handled by Syncer.
#
# By default, Syncer maintains PruningWindow number of headers. SyncFromHeight overrides this default,
# allowing any user to specify a custom starting point.
#
# SyncFromHeight has lower priority than SyncFromHash.
SyncFromHeight = 0
Please do not copy these values directly into the config -- please use the config-update command. Read the docs here.
By default, node maintains a sliding window of headers, bounded by Tail and Head headers. Requests with height below the Tail are rejected (This is, however, temporary, and lazy header fetching will be available with Backward Sync)
To retain the ability to request older queries with LNs, use new configuration fields to set an absolute header that the node will sync from, either the SyncFromHeight or the SyncFromHash field.
Pruning for Bridge and Full nodes is disabled. Currently, the p2p protocol for headers cannot distinguish between pruned and non-pruned serving node types. Therefore, to keep stable synchronization of historical headers, we disable pruned servers.
StartTimeout value in the config, as LN prunes on start. If the starting times out, e.g., with the default 20s, the node will attempt to persist the progress, but storage state corruptions may still occur. The complete mainnet header history pruning on moderate hardware takes under 100s, so update your config accordingly.StartTimeout value in the config, as LN syncs the difference during start. (This is, however, temporary, and asynchronous syncing that doesn't block start will be available with Backward Sync).
Daser.SampleFrom field is no longer supported. Use Header.Syncer.SyncFromHeight instead.Header.TrustedHash field is no longer supported. Use Header.Syncer.SyncFromHash instead.Header.TrustedPeriod field was removed and is now a network-level constant.Replace for go-datastore was added, which may break users depending directly on the node's go.mod.
Do the following in your project's root to fix:
go mod edit -replace github.com/ipfs/go-datastore=github.com/celestiaorg/go-datastore@48a63ae && go mod tidy. It's gonna be removed in future releases.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.3-arabica...v0.26.0-arabica
Nothing published for this version
…App v4/v5 mainnet update. Please review all breaking changes carefully before upgrading.
This release includes significant changes accumulated since May 2025 while waiting for the Celestia App v4/v5 mainnet update. Please review all breaking changes carefully before upgrading.
🚨 This release breaks both API and config!
--archival to keep full historyThis release contains configuration breaking changes. Node operators must run the config update command before starting their node:
celestia <node_type> config-update --p2p.network (or --node.store)
Changes:
“height”: 67374 becomes “height”: “67374”Migration: Update JSON parsing logic to handle integers as strings in header, share range, and blob commitment proof endpoints.
Changes:
Samples method now accepts height parameter directlyExtendedHeaderMigration:
// Before:
samples, err := client.Share.GetSamples(ctx, header)
// After:
samples, err := client.Share.GetSamples(ctx, height)
Changes:
GetSamples response now encoded as base64 stringsdata fieldGetRow and other methodsMigration:
// Before (v0.25.0-v0.25.1):
{
"share": {
"data": "AAAAAAA...base64..."
},
"proof": { ... }
}
// After (v0.25.2+):
{
"share": "AAAAAAA...base64...",
"proof": { ... }
}
Update JSON parsing to expect shares as direct base64 strings rather than nested objects.
Migration: If you were using the gateway, switch to direct API endpoints. Configure CORS policy using the new configurable CORS feature if needed.
Changes:
DataRootTupleRoot: String encoding changed from base64 to hex bytesDataRootTupleInclusionProof: Removed extra pointer (affects native Go API only, not JSON encoding)GetDataRootTupleRoot: Removed extra pointer in returned value (affects native Go API only)Migration:
Changes:
Migration: Update clients using range requests to use the new shwap protocol implementation.
Changes:
--archival flag to disable pruningMigration:
-archival flag when starting the node-experimental-pruning flag (pruning is now automatic)Rust ecosystem must upgrade to maintain RPC compatibility with v0.25.
Upgrade timeline:
header.GetRangeByHeight: upgrade immediately.updateHead by @santamasa in https://github.com/celestiaorg/celestia-node/pull/4191Addressing memory leak in light node (LN)
updateHead by @santamasa in https://github.com/celestiaorg/celestia-node/pull/4191arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4383mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4385mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4394kind:perf to assortment of required labels by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4419Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.24.1...v0.25.3
Fixes a potential memory leak in light node (LN) and allows disabling of sampling process (DASer).
Fixes a potential memory leak in light node (LN) and allows disabling of sampling process (DASer).
This patch release also requires a config update against the previous patch release. Please see docs for more information.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.2-mocha...v0.25.3-mocha
Fixes a potential memory leak in light node (LN) and allows disabling of sampling process (DASer).
Fixes a potential memory leak in light node (LN) and allows disabling of sampling process (DASer).
This patch release also requires a config update against the previous patch release. Please see docs for more information.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.2-arabica...v0.25.3-arabica
Nothing published for this version
This release accumulates all Arabica v0.25.x releases (v0.25.0–v0.25.2) and applies them to the Mocha testnet. It introduces several breaking API chan
This release accumulates all Arabica v0.25.x releases (v0.25.0–v0.25.2) and applies them to the Mocha testnet. It introduces several breaking API changes, new features, and critical updates for client developers (Go & Rust).
⚠ API Breaking Changes
Config Update Required – Run before starting if upgrading from < v0.25.0:
celestia <node_type> config-update
Data Retention Changes
Performance & Features – Faster GetRange via shwap (#4156, #4325), parallelized namespace data (#4420), optimized blob fetching (#4431).
Rust Users – Must upgrade to latest Rust crates for RPC compatibility (see section below).
config.toml, replaced with --archival flag (#4482)height, shares encoded as base64 (#4481, #4480)GetRange via shwap protocol (#4156, #4325)Rust ecosystem must upgrade to maintain RPC compatibility with v0.25.
Upgrade timeline:
header.GetRangeByHeight: upgrade immediately.Would you like me to also prepare a migration matrix (Node Operator vs Rust Client) with direct before/after code snippets (like we did for GetSamples)? That might help prevent mistakes during rollout.
This patch release includes additional API breaking changes that further improve consistency across the node API. Please review these changes carefull…
This patch release includes additional API breaking changes that further improve consistency across the node API. Please review these changes carefully before upgrading from v0.25.0 or v0.25.1.
⚠ Additional API Breaking Changes
--archival flag exclusively to disable pruningConfig Update Required (if upgrading from pre-v0.25.0)
celestia <node_type> config-update
Changes:
Migration:
--archival flag when starting the nodeChanges:
Samples method now accepts height parameter directlyExtendedHeaderMigration:
// Before:
samples, err := client.Share.GetSamples(ctx, header)
// After:
samples, err := client.Share.GetSamples(ctx, height)
Changes:
GetSamples response now encoded as base64 stringsdata fieldGetRow and other methodsMigration:
// Before (v0.25.0-v0.25.1):
{
"share": {
"data": "AAAAAAA...base64..."
},
"proof": { ... }
}
// After (v0.25.2+):
{
"share": "AAAAAAA...base64...",
"proof": { ... }
}
Update JSON parsing to expect shares as direct base64 strings rather than nested objects.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.1...v0.25.2
Full changelog from last release: https://github.com/celestiaorg/celestia-node/releases/tag/v0.25.0-arabica
Full changelog from last release: https://github.com/celestiaorg/celestia-node/releases/tag/v0.25.0-arabica
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.25.0-arabica...v0.25.1-arabica
Nothing published for this version
…App v4/v5 mainnet update. Please review all breaking changes carefully before upgrading.
This release includes significant changes accumulated since May 2025 while waiting for the Celestia App v4/v5 mainnet update. Please review all breaking changes carefully before upgrading.
⚠ API Breaking Changes
Config Update Required Run before starting:
celestia <node_type> config-update
Data Retention Changes
--archival to keep full historyAPI Enhancements – Configurable CORS, new client library, multi-endpoint tx submission
Faster GetRange – Uses shwap protocol for efficient partial retrieval
Performance Boosts – Parallelized namespace data; optimized blob retrieval
Bootstrap Updates – Added 01node mainnet bootstrap; removed outdated nodes
This release contains configuration breaking changes. Node operators must run the config update command before starting their node:
celestia <node_type> config-update --p2p.network (or --node.store)
Changes:
“height”: 67374 becomes “height”: “67374”Migration: Update JSON parsing logic to handle integers as strings in header, share range, and blob commitment proof endpoints.
Migration: If you were using the gateway, switch to direct API endpoints. Configure CORS policy using the new configurable CORS feature if needed.
Changes:
DataRootTupleRoot: String encoding changed from base64 to hex bytesDataRootTupleInclusionProof: Removed extra pointer (affects native Go API only, not JSON encoding)GetDataRootTupleRoot: Removed extra pointer in returned value (affects native Go API only)Migration:
Changes:
Migration: Update clients using range requests to use the new shwap protocol implementation.
Changes:
--archival flag to disable pruningMigration:
--archival flag to maintain full history--experimental-pruning flag (pruning is now automatic)updateHead by @santamasa in https://github.com/celestiaorg/celestia-node/pull/4191arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4383mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4385mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4394kind:perf to assortment of required labels by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4419Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.24.1...v0.25-arabica
deps(go.mod)!: Bump app to v5 by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4443
arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4445Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.5...v0.24.1
deps(go.mod): Bump app to mainnet by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4410
arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4445Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.5-mocha...v0.24.1-mocha
deps(go.mod): Bump app to mainnet by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4410
arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4445Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.5-arabica...v0.24.1-arabica
deps(go.mod)!: Bump app to v5 by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4443
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.5...v0.24.0-rc0
This release is the celestia-node release intended to be compatible with celestia-app v4 release.
This release is the celestia-node release intended to be compatible with celestia-app v4 release.
arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4369mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4372arabica (#4383) by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4384mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4386mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4395Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.22.3...v0.23.5
deps(go.mod): bump app dep and go-square by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4406
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.4-mocha...v0.23.5-mocha
deps(go.mod): backport app bump mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4395
mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4395Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.4-arabica...v0.23.5-arabica
deps(go.mod): backport arabica app bump by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4392
mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4395Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.3-mocha...v0.23.4-mocha
deps(go.mod): bump app mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4386
mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4386Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.3-arabica...v0.23.4-arabica
deps(go.mod): Bump app arabica (#4383) by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4384
arabica (#4383) by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4384mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4386Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.2-mocha...v0.23.3-mocha
deps(go.mod): Bump app --> mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4372
mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4372arabica (#4383) by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4384Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.2-arabica...v0.23.3-arabica
Please note this release rolls back a breaking go-header release so node operators may need to perform a config-update on their node in case they've u
Please note this release rolls back a breaking go-header release so node operators may need to perform a config-update on their node in case they've upgraded already.
See https://docs.celestia.org/how-to-guides/celestia-node-troubleshooting#resetting-your-config for more guidance.
arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4369mocha by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4372Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.1-mocha...v0.23.2-mocha
Please note this release rolls back a breaking go-header release so node operators may need to perform a config-update on their node in case they've u
Please note this release rolls back a breaking go-header release so node operators may need to perform a config-update on their node in case they've upgraded already.
See https://docs.celestia.org/how-to-guides/celestia-node-troubleshooting#resetting-your-config for more guidance.
arabica by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4369Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.1-arabica...v0.23.2-arabica
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release is config-breaking and requires go v1.24.1
This release is config-breaking and requires go v1.24.1
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.0-mocha...v0.23.1-mocha
This release is config-breaking and requires go v1.24.1
This release is config-breaking and requires go v1.24.1
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.23.0-arabica...v0.23.1-arabica
refactor(nodebuilder): Deprecation of Full Node Support by @walldiss in https://github.com/celestiaorg/celestia-node/pull/4248
storeEDS respects window param by @renaynay in https://github.com/celestiaorg/celestia-node/pull/4244Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.22.1...v0.23.0-rc0
This release corresponds with celestia-app's V4 upgrade.
This release corresponds with celestia-app's V4 upgrade.
Full Changelog: https://github.com/celestiaorg/celestia-node/compare/v0.22.2-mocha...v0.23.0-mocha
Nothing published for this version
Nothing published for this version
One column per quarter.