Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update module github.com/ethereum/go-ethereum to v1.14.12 #321

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

fix(deps): update module github.com/ethereum/go-ethereum to v1.14.12 #321

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/ethereum/go-ethereum v1.11.6 -> v1.14.12 age adoption passing confidence

Release Notes

ethereum/go-ethereum (github.com/ethereum/go-ethereum)

v1.14.12: Gei Hinnom (v1.14.12)

Compare Source

This release covers quite a lot of time, and has many changes across the codebase. In particular; changes in tracing and account management, optimizations in database, trie and evm, and, as always bugfixes.

This release removes the personal RPC namespace. It was already previously deprecated, and has not been accessible by default for nearly two years. We also removed the --unlock command-line parameter, with a view towards removing key/account management from the geth binary.

  • Key management:
    • Remove --unlock command line flag from geth (#​30737)
    • Remove personal RPC namespace (#​30704)
  • Builds:
  • Tracing:
    • invoke OnCodeChange-hook on selfdestruct (#​30686, #​30497)
    • improvements to flatCallTracer (#​30539)
    • invoke tx-end hook in runtime helpers (#​30711)
    • disableCode and disableStorage options for prestateTracer (#​30648)
    • tracing of system calls (#​30666)
    • Change to how chainconfig is passed to tracers (breaking change) (#​30540)
    • add GetTransientState method to StateDB interface (#​30531)
  • Signing:
    • improved support for EIP-712 array types (#​30620)
    • non-legacy transactions support for ledger wallets (#​30180)
  • Bugfixes:
    • Set basefee for AccessList based on given block, not chain tip (#​30538)
    • Multiple issues in benchmarks (#​30667)
    • Fix bug with resolving a payload (#​30615)
  • Database optimizations
    • Run pebble in non-sync mode (#​30573, #​29792). This change makes quite a big difference on certain OS:es, particularly MacOSX/Darwin, where
      it has been noted that fsync is notoriously slow.
    • Use to increasing level sizes (#​30602), This change makes pebble use larger files, reducing the number of files from 160K to 10K.
  • Assorted:
    • Make jwtsecretflag expand tilde
    • Work on verkle (#​30672)
    • Work on EIP-7002 and EIP 7251 (#​30571)
    • Implement EIP-7685 and EIP-6110 (flat requests enconding) (#​30425)
    • Validation of EOF containers (#​30418)
    • More helpful responses for rejected transactions (#​30715)
    • Work on cross-execution witness (#​30698)
    • EVM speed optimizations (#​30662, #​30629)
    • Reduce peak memory usage during reorg (#​30600)
    • Speed up trie commit via concurrent workers (#​30545)
    • Fuzzing improvments (#​30585)
    • Implement new engine_getBlobsV1 API method (#​30537)

For a full rundown of the changes please consult the Geth 1.14.12 release milestone.

As with all our previous releases, you can find the:

v1.14.11: Makhaira (v1.14.11)

Compare Source

This is a minor release, with the primary goal of publishing new stable and latest docker images. A problem in the CI pipeline prevented the publishing of docker images. We have now resolved the problem, and hope that the v1.14.11-release will be published as usual on Docker hub.

We have now switched the way the docker images are built, and the -amd64 and -arm64-tagged versions will no longer be maintained:

  • alltools-latest-amd64, alltools-latest-arm64 -> alltools-latest
  • latest-amd64,latest-arm64 -> latest
  • v1.14.10-amd64, v1.14.10-arm64 -> v1.14.10

NOTE: If you are a docker user on stable/latest, there's a high chance that you are not using any of the last two releases. If so, you are advised to look through the release-notes of those releases respectively: v1.14.10 and v1.14.9.

Other changes since v1.14.10 include

  • Remove totalDifficulty field from RPC, in accordance with spec update, #​30386
  • Fix flaw in simulated backend #​30465
  • New method of building multi-platform docker images #​30530
  • Ability to disable FINDNODE liveness checks in tests #​30512

For a full rundown of the changes please consult the Geth 1.14.11 release milestone.

As with all our previous releases, you can find the:

v1.14.10: Kopis (v1.14.10)

Compare Source

Geth v1.14.10 is a hotfix release to fix a blob pool regression introduced in v1.14.9. Users running the previous bad version should update ASAP. That said, there is no immediate danger to these users, just to the health of blob transaction propagation and inclusion in the network.

Beside the hotfix, this release:

  • Ships stateless witness production and verification into the engine API (#​30069).
  • Use 0 global gas cap as unlimited in simulated calls too (#​30474, #​30496).

For a full rundown of the changes please consult the Geth 1.14.10 release milestone.

As with all our previous releases, you can find the:

v1.14.9: Aegis (v1.14.9)

Compare Source

This release has been nuked. It broke the blob pool, please do not use it.

This is a maintenance release, but also introduces support for the new multicall spec, which is a much anticipated feature providing a eth_simulateV1 call, that takes a list of blocks and executes them as if calling multiple eth_calls sequentially. It accepts optional state and precompile overrides, as well as transfer log events. This release also ships with improved verkle support.

Command line

Pectra

Core

Txpool

  • Fetch transactions from a peer in the order they were announced in order to minimize nonce gap, causing blob txs to rejected. A special rule is applied to blob transactions: they are retrieved from the network upon reception of the announcement, as blob transactions are never broadcast over the p2p network (https://github.com/ethereum/go-ethereum/pull/30125)

Networking

RPC / tracing

Misc

Build

Full Changelog: ethereum/go-ethereum@v1.14.8...v1.14.9

For a full rundown of the changes please consult the Geth 1.14.9 release milestone.

As with all our previous releases, you can find the:

v1.14.8: Rayingri (v1.14.8)

Compare Source

This is a maintenance release with bug fixes only.

Command changes
  • Blobpool related flags in Geth now actually work. (#​30203)
  • The evm run command no longer overwrites the sender account in genesis.json. (#​30259)
  • evm run now allows configuring baseFeePerGas in genesis.json. (#​30281)
Go API
  • core/types.Transaction.ChainID had a bug where it modified the signature for very large ChainID (>= 2^64). (#​30157)
  • ethclient.Client.NetworkID now supports values returned in hex format by the server. (#​30263)
  • ethclient/simulated.Backend.AdjustTime was fixed to apply the correct time divison. (#​30138)
  • accounts/abi/bind.TransactOpts now supports setting an access list for created transactions. (#​30195)
  • The package p2p/simulations has been removed. (#​30250)
Core
  • A snap-sync database corruption related to sync restarts is fixed in this release. (#​30258)
  • eth_call storage overrides now work as originally intended: if a storage replacement object is specified in the call, previous storage values of the account are cleared. (#​30185)
  • The txpool did not use the transaction's inline sender cache in some cases. (#​30208)
  • The performance of EVM stack swaps was improved a bit. (#​30249)
Networking
  • The downloader now takes withdrawals into account when sizing its queue. (#​30276)
  • The new discovery node revalidation could hot-spin in certain rare scenarios. (#​30239)
  • Configuring an external IP using --nat=extip:... could lead to invalid discovery packets being generated. (#​30234)
Build
  • github.com/btcsuite/btcd/btcec has been upgraded to resolve a build error caused by upstream API changes. (#​30181)
  • Previous releases will not build with Go 1.23, but this one will. (#​30253)
  • This release is built with Go 1.22.6. (#​30273)

For a full rundown of the changes please consult the Geth 1.14.8 release milestone.

As with all our previous releases, you can find the:

v1.14.7: Trident (v1.14.7)

Compare Source

This is a hot-fix release for a bug (#​30139) which affects only the previous release. Users of v1.14.6 are kindly requested to update.

For a full rundown of the changes please consult the Geth 1.14.7 release milestone.

As with all our previous releases, you can find the:

v1.14.6: Talaria (v1.14.6)

Compare Source

Geth v1.14.6 is a maintenance release, but it does ship with the experimental witness building validation code used in @​karalabe's "cross validation" proposal. Note that the engine API part is not included in this release.

Shipped features:

Shipped bugfixes:

  • Fix issue in which the beacon root contract balance would not be saved in developer mode, causing an error on restart (#​29963)
  • Fix shutdown crash when geth runs in blsync mode (#​29946)
  • Fix data races in snapshot access (#​30001, #​30011)
  • Fix out of bounds access in json unmarshalling (#​30014)
  • Add missing lock in peer discovery (#​29960)

For a full rundown of the changes please consult the Geth 1.14.6 release milestone.

As with all our previous releases, you can find the:

v1.14.5: Bothros (v1.14.5)

Compare Source

Geth v1.14.5 is a hotfix release that addresses a regression introduced in v1.14.4, which prevented the node from discovering other peers in certain networking setups (#​29944). It is otherwise identical to v1.14.4.

Geth v1.14.4 in a usual maintenance release, but it does ship a 5-7% block import speed improvement. Furthermore, v1.14.4 also finally includes an Ether supply live tracer, that you can enable via --vmtrace supply. Also please note, the default value for miner tip enforcement was dropped from 1 gwei to 0.001 gwei (block producers can change this via --miner.gasprice).

Shipped features:

Shipped bugfixes:

  • Fix a gas estimation regression that caused longer runtimes (#​29738).
  • Fix a potential crash in JSON logging for EVM blocktests (#​29795).
  • Fix utility commands to support post-merge opcodes (#​29799).
  • Fix a txpool synchronicity issue in simulated chains (#​29876).
  • Fix a iteration order when using a trie node iterator (#​27838).
  • Fix a TCP/UDP discovery port test in cmd/devp2p (#​29879).
  • Fix IPv6 endpoint determination (#​29801, #​29827).

For a full rundown of the changes please consult the Geth 1.14.4 release milestone.

As with all our previous releases, you can find the:

v1.14.4: Triodia (v1.14.4)

Compare Source

Geth v1.14.4 in a usual maintenance release, but it does ship a 5-7% block import speed improvement. Furthermore, v1.14.4 also finally includes an Ether supply live tracer, that you can enable via --vmtrace supply. Also please note, the default value for miner tip enforcement was dropped from 1 gwei to 0.001 gwei (block producers can change this via --miner.gasprice).

Shipped features:

Shipped bugfixes:

  • Fix a gas estimation regression that caused longer runtimes (#​29738).
  • Fix a potential crash in JSON logging for EVM blocktests (#​29795).
  • Fix utility commands to support post-merge opcodes (#​29799).
  • Fix a txpool synchronicity issue in simulated chains (#​29876).
  • Fix a iteration order when using a trie node iterator (#​27838).
  • Fix a TCP/UDP discovery port test in cmd/devp2p (#​29879).
  • Fix IPv6 endpoint determination (#​29801, #​29827).

For a full rundown of the changes please consult the Geth 1.14.4 release milestone.

As with all our previous releases, you can find the:

v1.14.3: Fuel Depot (v1.14.3)

Compare Source

We're issuing this (v1.14.3) release to finally publish v1.14 on the Ubuntu PPA. It is otherwise identical to v1.14.2.

This is a maintenance release containing bug-fixes. In case you are wondering where v1.14.1 (and v1.14.2) went, let's just say, the continuous integration gods have not been good to us.

List of changes in detail:

Geth
  • When using geth --dev with a custom genesis block, the genesis file must now set difficulty and terminal total difficulty to zero. (#​29579)
  • For fork scheduling errors in geth init, fork timestamps will now be printed correctly. (#​29514)
  • Certain aspects of state handling are now parallelized resulting in a 5-10% speedup for block processing. (#​29681)
RPC
  • eth_feeHistory was changed to apply a limit on the number of requested percentiles (#​29644)
  • eth_createAccessList now honors request cancellation and terminates background work (#​29686)
  • eth_estimateGas takes tx blobs into account for low-balance scenarios (#​29703)
Tracing
  • The live tracing interface has new hooks around EVM system calls (#​29355)
  • flatCallTracer was fixed to return the correct error result when interrupted (#​29623)
Build

For a full rundown of the changes please consult the Geth 1.14.1 release milestone.

As with all our previous releases, you can find the:

v1.14.2: Ker (v1.14.2)

Compare Source

This is a maintenance release containing bug-fixes. In case you are wondering where v1.14.1 went, let's just say, the continuous integration gods have not been good to us.

List of changes in detail:

Geth
  • When using geth --dev with a custom genesis block, the genesis file must now set difficulty and terminal total difficulty to zero. (#​29579)
  • For fork scheduling errors in geth init, fork timestamps will now be printed correctly. (#​29514)
  • Certain aspects of state handling are now parallelized resulting in a 5-10% speedup for block processing. (#​29681)
RPC
  • eth_feeHistory was changed to apply a limit on the number of requested percentiles (#​29644)
  • eth_createAccessList now honors request cancellation and terminates background work (#​29686)
  • eth_estimateGas takes tx blobs into account for low-balance scenarios (#​29703)
Tracing
  • The live tracing interface has new hooks around EVM system calls (#​29355)
  • flatCallTracer was fixed to return the correct error result when interrupted (#​29623)
Build

For a full rundown of the changes please consult the Geth 1.14.1 release milestone.

As with all our previous releases, you can find the:

v1.14.0: Asteria (v1.14.0)

Compare Source

Geth v1.14.0 (Asteria) is a major release with some juicy new features as well as some breaking changes. Please read through the release notes before updating to it. Whilst it should not adversely impact most users, there're always those rare occurrences.

Highlights

  • Geth v1.14.0 switches over the default state trie representation from hash mode to path mode (i.e. --state.scheme flipped form hash to path) (#​29108). This change does not affect Geth instances with pre-existing databases, in the case of which Geth continues to use whatever the existing database's format is. If no previous database exists however, for full nodes, Geth will now default to pathdb. The main advantage is built-in, online historical state pruning; no more runaway state growth.

    • If you want to force the old behaviour, you can run Geth with --state.scheme=hash for now. That said, we will be dropping hash mode sooner rather than later, so we advise everyone running full nodes to gradually switch, if they haven't yet.
    • Archive mode support is not yet finalised for path mode, so archive nodes will still run in hash mode. Naturally, hash mode will not be dropped until a full path archive lands and people have enough time to switch to it.

  • Geth v1.14.0 introduces a brand new live-tracing feature, where one or more transaction tracers might be injected into the block processing pipeline, ensuring that tracing and execution happen in lockstep (#​29189). Since Go does not have a cross platform, OS native plugin infrastructure, adding live tracers needs to be done at the Geth source code level, and Geth itself subsequently rebuilt. That said, the advantage is that such tracers have full execution flexibility to do whatever they like and however they like. Please see the live-tracer changelog and docs for details.

    • Live tracing runs in lockstep with block execution, one waiting for the other. You should never run a live tracer on a validating node, or any other where latency is important. The recommended practice is to have tracers collect and export the bare minimum data needed and do any post-processing in external systems where latency is not relevant.
    • The live tracer work required a number of breaking internal API changes. If you had your own native tracers implemented before this change, the changelog contains the necessary steps needed to update your old code for the new APIs.

  • Geth v1.14.0 replaces the completely random transaction propagation paths (in the Ethereum P2P network) with pseudo-random ones, that ensure transactions from the same account follow the same path in the network (as long as no peer churn happens). The purpose is to allow a burst of transactions from the same account to ripple through the network on the same connections, minimising reordering. Whilst this doesn't provide any guarantees, nor does it replace the potential need for more complex routing logic, it should make nonce gaps significantly less likely, reducing the probability of dropped transactions during bursts (#​29034).

    • This change only applies to networking, so other clients are not required to follow suit. That said, the network would behave more consistently overall if all clients implemented some similar logic (the exact routing algorithm is irrelevant, as long as it's stable in the accounts).

  • Geth v1.14.0 drops support for running pre-merge networks (#​29169). This does not mean that Geth will not be able to process or validate pre-merge blocks, rather that starting v1.14.0, Geth must have a consensus client drive it's chain selection. Geth drops the forward-sync mode of operation, where it imports blocks based on PoW (ethash) or PoA (clique) difficulties.

    • Non-merged networks will need to stick to Geth v1.13.x until they transition to post-merge. As Ethereum has transitioned towards a post-merge world, we cannot maintain a significant chunk of code that's been dead for 2 years now on mainnet.
    • Post-merge networks must be marked so with the terminalTotalDifficultyPassed: true field in their genesis.json. This requirement will be dropped (along with even caring at all about this field) in a few releases, but for now this field produces a clear error message for the user of what's wrong with their pre-merge network.

  • Geth v1.14.0 stops automatically constructing the pending block (#​28623). Performance wise there is a significant cost to creating a potential pending block, yet most node operators do not care about it. Not even validators need the pending block. This work also drops support for mining/signing a block "off-demand" (i.e. not via the engine API, rather by Geth itself), meaning Clique signing is also removed going forward.

    • With Clique mining removed, Geth v1.14.0 cannot be a Clique signer any more. This however goes hand-in-hand with the removal or pre-merge chain selection and synchronisation support described earlier.
    • The pending block can still be constructed on demand for now. Whenever an RPC method is called that is based on the pending block, Geth will generate it on the fly and cache it for 1 second for subsequent calls. The first such call will have a few hundred ms execution delay.

  • Geth v1.14.0 removes support for filtering pending logs. This is following the previous change of creating the pending block only on demand. We see next to no value in monitoring the logs of a random subset of transactions that might (but probably mostly will not) end up in the next block. Power users who wish to monitor the transaction pool for MEV (or similar) purposes, should hook into Geth directly and extract the exact data they need, rather than rely on insufficient API endpoints.

  • Geth v1.14.0 ships a beacon chain light client (#​28822, #​29308, #​29335, #​29532, #​29567). It uses the REST API of beacon nodes and requires the beacon / light_client namespace, currently supported by Lodestar and Nimbus (specs).

    • The beacon light client provides access to consensus layer data, not execution layer data. This currently means that it can follow the beacon chain as a light client and extract the latest head and finalised execution layer block. That can be used to drive a full execution node without running an own beacon node. There is no support yet for a full execution light client.
    • Validation and staking is not possible with a beacon light client. Since the sync committee signatures on each beacon head are canonised in the next block, the beacon light client can only follow the chain with one slot delay.
    • The beacon light client exists both as a standalone executable and integrated into Geth. The blsync executable can drive any execution layer node through the standard engine API or can just do a "test run" printing block numbers and hashes to the console. The integrated mode can do the same inside Geth. If you specify at least one suitable consensus layer REST API endpoint with the --beacon.api flag, then Geth will run without a beacon node connected through the engine API.

  • Geth v1.14.0 switched to using Go v1.22 by default (#​28946), which means we've dropped support for Go v1.20. Geth also started using of new features from Go v1.21 in our codebase, so building with Go v1.20 will probably error from now on. Just a heads up.

Features
  • Add the geth db inspect-history command to inspect pathdb state history (#​29267).
  • Enable the Cancun hard-fork when running Geth in dev mode (#​28829).
  • Use beacon chain finality as the marker to move old blocks into ancients (#​28683).
  • Drop large-contract (500MB+) deletion DoS protection from pathdb post Cancun (#​28940).
  • Switch Geth's USB library from libusb to hid for simpler hardware wallet support (#​28945, #​29175, #​29176).
  • Update the prestateTrancer to take into account 4844 blobs and their fees (#​29168).
  • Extend the ethclient and gethclient packages with support for 4844 blob fields (#​29198).
  • Detailed block execution metrics are now always reported, deprecating --metrics.expensive (#​29191).
  • Avoid a lot of memory allocations while shuffling 4844 blobs within Geth (#​29050).
  • Switch to using Go's native log/slog package instead of golang/exp (#​29302).
  • When computing state roots, apply state updates before deletes to avoid some trie lookups. (#​29201).
  • Track not only total peer count, but also how many are inbound or outbound (#​29424).
  • Add support for signing blob transactions (#​28976, #​29470).
  • Surface max initcode exceeded errors from the VM to outer callers (#​29354).
  • Update the EVM to reject contract creation on top of non-empty storage (#​28912).
  • Switch over the BLS implementation from kilic to gnark (#​29441).
  • Start emitting performance degradation warnings if pebble is overloaded (#​29478).
  • Add eth_blobBaseFee RPC method, extend eth_feeHistory with blobs (#​29140).
Bugfixes
  • Shave an allocation off of pathdb trie writes caused by a bad initial buffer size (#​29106).
  • Fix a crash in dev mode using pathdb when rewinding more than 128 blocks (#​29107).
  • Fix some non-conformance issues in the engine API's error returns (#​29115).
  • Fix a too early db close in geth dump and geth snapshot dump (#​29100).
  • Fix the devp2p command to not ignore specified bootnodes (#​29091).
  • Fix the prestateTracer to return the correct nonce for contract creations (#​29099).
  • Fix blob fee formatting on RPC output from decimal to hexadecimal (#​29166).
  • Fix the blob pool tx acceptance error if it is already known vs underprices (#​29210).
  • Fix a few Windows file path joining issues in various go-ethereum utilities (#​29227, #​29479, #​29489).
  • Fix a data race when tracing a block via the JavaScript tracers (#​29238).
  • Fix a number of chain rewinding corner-cases after crashes (#​29196, #​29245).
  • Fix an ENR RLP decoding issue in the devp2p command (#​29257).
  • Fix withdrawal collection for simulated chains and dev mode (#​29344).
  • Fix a snap sync corner-case in hashdb mode (#​29341).
  • Fix an engine API field name mismatch for GetClientVersion (#​29351).
  • Fix a maximum unix socket path length check on macos (#​29385).
  • Fix an issue in the blob-pool that prevented Geth to start after a crash (#​29451).
  • Fix an issue that caused the JSON loggers to discard some log level (#​29471).
  • Fix the (now post-merge) genesis block difficulty in dev mode (#​29469).
  • Fix the precompile addresses of BLS ops (not live code yet) (#​29445).
  • Fix a data race that sometimes returned reorged receipts (#​29343).
  • Fix a snap-sync restart quirk that sometimes resulted in redownloading some data (#​29378).
  • Fix a snap-sync restart quirk that sometimes resulted in corrupting some data (#​29313).
  • Fix ancient header reader to hard cap at 2MB (network soft limit) (#​29534).
  • Fix the topic filtering to enforce some sanity nesting limits (#​29535).

We'd also like to shout out to a very high number of authors sending many nitpick PRs. Whilst we are not entirely sure about the intent behind these PRs (commit farming and all), we are nonetheless happy that the Geth codebase gets better.

For a full rundown of the changes please consult the Geth 1.14.0 release milestone.

As with all our previous releases, you can find the:

v1.13.15: Ontamalca (v1.13.15)

Compare Source

Geth v1.13.15 is a maintenance-release that contains some fixes mainly to avoid snapsync-related data-corruption.

We recommend all users to upgrade to v1.13.15 as soon as possible.

As with all our previous releases, you can find the:

v1.13.14: Altaaya (v1.13.14)

Compare Source

Geth v1.13.14 is a small maintenance release with a handful of polishes to the blob pool:

  • Disallow blob transactions below the protocol minimum of 1 wei to enter the pool (#​29081).
  • Reduce the blob pool's max capacity to 2.5GB for the rollout. (#​29090).
  • Fix gas estimation for blob transactions (#​29085).

This release is NOT critical for the Cancun fork, but recommended to make Geth lighter in anticipation to unknown blob load.

Other fixes:

  • Support overriding the basefee during tracing (#​29051).
  • Fix call tracers missi

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner December 19, 2023 12:22
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 495a457 to 0f848cc Compare December 19, 2023 15:06
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.6 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.7 Dec 19, 2023
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 0f848cc to bc8f34a Compare December 22, 2023 17:08
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.7 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.8 Dec 22, 2023
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from 4b286d2 to c33c0a5 Compare January 3, 2024 15:14
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from 595757f to f0644d5 Compare January 11, 2024 18:52
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.8 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.10 Jan 11, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from f0644d5 to 1128bcf Compare January 15, 2024 11:18
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 1128bcf to 74928cd Compare January 24, 2024 13:48
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.10 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.11 Jan 24, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from 05285de to 8d31749 Compare February 9, 2024 09:43
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.11 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.12 Feb 9, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 8d31749 to 379047f Compare February 21, 2024 15:29
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.12 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.13 Feb 21, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 379047f to 2dde941 Compare February 27, 2024 13:21
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.13 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 Feb 27, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 2dde941 to d141c5c Compare February 29, 2024 12:29
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from 789e1e2 to 6da2dea Compare April 3, 2024 08:08
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 3 times, most recently from 28895d9 to 23c7546 Compare April 17, 2024 08:47
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.13.14 fix(deps): update module github.com/ethereum/go-ethereum to v1.13.15 Apr 17, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from 0bca2e2 to 8b84837 Compare April 19, 2024 13:11
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from a14a108 to a4f963a Compare May 8, 2024 16:57
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.0 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.2 May 8, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from a4f963a to eccf1f7 Compare May 9, 2024 11:22
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.2 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.3 May 9, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from eccf1f7 to 969ec74 Compare May 20, 2024 16:52
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from 9388cfd to a3cfa28 Compare May 30, 2024 17:39
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from a3cfa28 to d28ee9a Compare June 5, 2024 11:43
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.3 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.4 Jun 5, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 5, 2024 •
edited
Loading

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 14 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21.5 -> 1.23.3
google.golang.org/protobuf v1.31.0 -> v1.34.2
github.com/cespare/xxhash/v2 v2.2.0 -> v2.3.0
github.com/deckarep/golang-set/v2 v2.1.0 -> v2.6.0
github.com/go-ole/go-ole v1.2.6 -> v1.3.0
github.com/golang/protobuf v1.5.3 -> v1.5.4
github.com/holiman/uint256 v1.2.2-0.20230321075855-87b91420868c -> v1.3.1
github.com/tklauser/go-sysconf v0.3.10 -> v0.3.12
github.com/tklauser/numcpus v0.4.0 -> v0.6.1
golang.org/x/crypto v0.21.0 -> v0.22.0
golang.org/x/net v0.23.0 -> v0.24.0
golang.org/x/sync v0.6.0 -> v0.7.0
golang.org/x/sys v0.18.0 -> v0.22.0
golang.org/x/term v0.18.0 -> v0.19.0
gopkg.in/check.v1 v1.0.0-20200902074654-038fdea0a05b -> v1.0.0-20201130134442-10cb98267c6c

@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from d28ee9a to 5cd51a3 Compare June 6, 2024 15:36
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.4 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.5 Jun 6, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 5cd51a3 to 500905d Compare June 11, 2024 13:52
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 500905d to e7b093e Compare July 2, 2024 19:11
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.5 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.6 Jul 2, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from e7b093e to d92e432 Compare July 11, 2024 14:30
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.6 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.7 Jul 11, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from d92e432 to 56f7d85 Compare August 12, 2024 13:37
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.7 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.8 Aug 12, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 56f7d85 to 60d8333 Compare September 18, 2024 18:26
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.8 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.9 Sep 18, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch 2 times, most recently from e0abbd0 to 9901032 Compare September 27, 2024 12:27
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.9 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.10 Sep 27, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 9901032 to 4dc9a03 Compare October 1, 2024 16:13
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.10 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.11 Oct 1, 2024
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from 4dc9a03 to c62cb07 Compare November 17, 2024 15:09
@renovate renovate bot force-pushed the renovate/github.com-ethereum-go-ethereum-1.x branch from c62cb07 to 912d2fe Compare November 19, 2024 15:02
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.14.11 fix(deps): update module github.com/ethereum/go-ethereum to v1.14.12 Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate-bot
Projects
Core Kanban
Status: Waiting Review
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@gordsport