Skip to content

chore(deps): update dependency nethermindeth/nethermind to v1.39.3 - #796

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
renovate/ethereum-clients
Open

chore(deps): update dependency nethermindeth/nethermind to v1.39.3#796
github-actions[bot] wants to merge 1 commit into
mainfrom
renovate/ethereum-clients

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
NethermindEth/nethermind patch 1.39.21.39.3

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

NethermindEth/nethermind (NethermindEth/nethermind)

v1.39.3

Compare Source

[!IMPORTANT]
This is a mandatory update for all node operators. Please upgrade at your earliest convenience.

Release notes

A patch release on top of 1.39.2 with reliability and hardening fixes across block processing, networking, and request decoding. No consensus or database-format changes, so it's a drop-in upgrade from any 1.39.x version.

Overview

3 changes since 1.39.2:

  • Hardened ABI decoding against malformed input (#​12588)
  • Fixed pooled-memory cleanup in block processing and networking (#​12034)
  • Reduced allocations in EIP-6110 deposit-request decoding (#​12185)

What's Changed

Full Changelog: NethermindEth/nethermind@1.39.2...1.39.3

Build signatures

The packages are signed with the following OpenPGP key: AD12 7976 5093 C675 9CD8 A400 24A7 7461 6F1E 617E


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@bussyjd bussyjd mentioned this pull request Jul 20, 2026
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch 6 times, most recently from 9fb5519 to d0aa770 Compare July 27, 2026 20:30
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch 2 times, most recently from be8dc97 to 2b50694 Compare July 29, 2026 15:38
bussyjd added a commit that referenced this pull request Aug 5, 2026
Applied directly rather than merging the PR branches: all four are cut
from main while this branch carries newer intermediate versions from
rc1's own renovate merges, so every one of them conflicts on every file
it touches. Hand-resolving those conflicts is how a dependency silently
gets downgraded, so the target versions are applied in one commit
instead — the same shape renovate would emit if it rebased onto rc2.

obolup.sh (#797):
- kubectl 1.36.2 -> 1.36.3, helmfile 1.7.1 -> 1.7.2,
  helm-diff 3.15.10 -> 3.15.11, ollama 0.32.1 -> 0.32.5

ethereum clients (#796):
- geth v1.17.4 -> v1.17.5, nethermind 1.39.1 -> 1.39.2,
  besu 26.7.0 -> 26.7.1, erigon v3.5.2 -> v3.5.4,
  lighthouse v8.2.0 -> v8.2.1, prysm v7.1.7 -> v7.1.8,
  lodestar v1.44.0 -> v1.45.0
  (reth and teku were already at target; nimbus tracks a different
  renovate datasource and had no PR, so it is left alone)

scalar (#795):
- @scalar/api-reference 1.62.9 -> 1.64.0 with its matching SRI hash,
  which must move in lockstep or the browser blocks the script

cloudflared (#794):
- 2026.7.2 -> 2026.7.3 with its matching image digest
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch from 2b50694 to 8389ee1 Compare August 6, 2026 14:47
@github-actions
github-actions Bot force-pushed the renovate/ethereum-clients branch from 8389ee1 to f15757b Compare August 8, 2026 15:07
@github-actions github-actions Bot changed the title chore(deps): update ethereum el/cl client updates chore(deps): update dependency nethermindeth/nethermind to v1.39.3 Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant