chore(deps): update ethereum el/cl client updates - #825
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
renovate/ethereum-clients
branch
3 times, most recently
from
August 20, 2026 13:19
3075fdd to
a816f4c
Compare
bussyjd
enabled auto-merge
August 22, 2026 22:35
github-actions
Bot
force-pushed
the
renovate/ethereum-clients
branch
from
August 24, 2026 19:13
a816f4c to
4436a8e
Compare
github-actions
Bot
force-pushed
the
renovate/ethereum-clients
branch
3 times, most recently
from
September 2, 2026 18:06
24af408 to
44e6688
Compare
github-actions
Bot
force-pushed
the
renovate/ethereum-clients
branch
2 times, most recently
from
September 15, 2026 18:06
1fef094 to
724eaa6
Compare
github-actions
Bot
force-pushed
the
renovate/ethereum-clients
branch
from
September 17, 2026 03:06
724eaa6 to
b36af05
Compare
github-actions
Bot
force-pushed
the
renovate/ethereum-clients
branch
from
September 17, 2026 14:06
b36af05 to
1fdefcf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.45.0→v1.48.026.7.1→26.9.01.39.2→1.39.3v3.5.4→v3.6.126.7.1→26.8.1v2.4.1→v2.6.0v8.2.1→v8.2.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
ChainSafe/lodestar (ChainSafe/lodestar)
v1.48.0Compare Source
Good day Lodestar operators! We’ve just released v1.48.0, a strongly recommended upgrade for mainnet and testnet users.
This release introduces flat-file storage for PeerDAS data columns, reducing LevelDB pressure and making data-column serving more efficient for finalized and retained column data.
Highlights
Flat-file storage for data columns: Newly persisted PeerDAS data columns are now stored as flat files under
$dataDir/data_columnsby default, with--dataColumnDiravailable if operators want to place them on a separate volume. (#8899)More efficient data-column reads: The new format stores columns with per-column indexing and compression, so Lodestar can read requested columns directly instead of loading every column for a block. (#8899)
No manual migration required: Existing LevelDB column data remains available as an upgrade fallback, while newly persisted data columns use the flat-file path. Blob sidecar storage is unchanged. (#8899)
Click here for the full changelog
Features
Bug Fixes
Performance
Refactoring
Dependencies
Tests
Maintenance
Documentation
v1.48.0-rc.0Compare Source
Changelog
Full Changelog
Features
Bug Fixes
Performance
Refactoring
Dependencies
Tests
Maintenance
Documentation
v1.47.0Compare Source
Good day Lodestar operators! We've just release v1.47.0 and recommend you upgrade your mainnet and testnet nodes. This one is BIG! We have moved our bls operations to Zig!! 🎉🎉 We are super proud to bring the first of many Zig releases to you as you will definitely notice performance benefits. But wait, there's more!!
We have been hunting for a bug in libp2p for a while, one that prevented graceful shutdown and this release has finally squashed that bug dead! You should not see any more issues with hanging shutdowns.
This is on top of all the work we've done to get ready for Glamsterdam. And ready we are. There is still some stuff you will see in the next release but for the most part your clients will be ready to rock and roll for the next fork. We just need to wait for scheduling to add the fork transition epochs into the codebase. Stay tuned...
We love you all and thank you for standing with us while we laid the foundation for a Zig encrusted future. We look forward to the next pieces that we will release and are excited to bring you more news in upcoming versions. Its going to be legen-wait-for-it-dary...
Full Changelog
Features
Bug Fixes
Performance
Refactoring
Dependencies
Continuous Integration
Tests
Styles
Maintenance
Documentation
v1.47.0-rc.0Compare Source
Changelog
Full Changelog
Features
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate.