fix(deps): update module github.com/ethereum/go-ethereum to v1.14.12 - autoclosed #13
+143
−36
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
fc006f9 to
dd05b40
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
2 times, most recently
from
be958d1 to
87a9a97
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
87a9a97 to
29ea9fc
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
29ea9fc to
a690c1c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
a690c1c to
bad94e7
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
bad94e7 to
fa37684
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
2 times, most recently
from
ca55325 to
93b983a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
93b983a to
0b19c7d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
0b19c7d to
818554c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
818554c to
add07ad
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
add07ad to
a81666e
Compare
renovate
bot
changed the title
ℹ Artifact update noticeFile name: packages/airdrop/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
a81666e to
1c4e185
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
1c4e185 to
ec80c3e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
ec80c3e to
2781eb3
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
2781eb3 to
b4b6b1d
Compare
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
b4b6b1d to
8ecdde1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
8ecdde1 to
b2aa8f3
Compare
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
b2aa8f3 to
59dbf3c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
59dbf3c to
5e6707e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
5e6707e to
01512dc
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
2 times, most recently
from
0f18785 to
03ec9e2
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
03ec9e2 to
92d2e0f
Compare
renovate
bot
changed the title
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.13.2->v1.14.12Release 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
personalRPC namespace. It was already previously deprecated, and has not been accessible by default for nearly two years. We also removed the--unlockcommand-line parameter, with a view towards removing key/account management from thegethbinary.--unlockcommand line flag fromgeth(#30737)personalRPC namespace (#30704)24.10(#30580)flatCallTracer(#30539)disableCodeanddisableStorageoptions forprestateTracer(#30648)GetTransientStatemethod to StateDB interface (#30531)AccessListbased on given block, not chain tip (#30538)it has been noted that
fsyncis notoriously slow.EIP-7002andEIP 7251(#30571)EIP-7685andEIP-6110(flat requests enconding) (#30425)engine_getBlobsV1API 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:
ethereum/client-go.v1.14.11: Makhaira (v1.14.11)Compare Source
This is a minor release, with the primary goal of publishing new
stableandlatestdocker images. A problem in the CI pipeline prevented the publishing of docker images. We have now resolved the problem, and hope that thev1.14.11-release will be published as usual on Docker hub.We have now switched the way the docker images are built, and the
-amd64and-arm64-tagged versions will no longer be maintained:alltools-latest-amd64,alltools-latest-arm64->alltools-latestlatest-amd64,latest-arm64->latestv1.14.10-amd64,v1.14.10-arm64->v1.14.10NOTE: 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
totalDifficultyfield from RPC, in accordance with spec update, #30386FINDNODEliveness checks in tests #30512For 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:
ethereum/client-go.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:
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:
ethereum/client-go.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_simulateV1call, that takes a list of blocks and executes them as if calling multipleeth_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
Networking
RPC / tracing
eth_simulateV1, which allows for the simulation a chain of blocks or simply a processing a sequence of eth_calls in one go. It is the implementation of the latest multicall spec (https://github.com/ethereum/go-ethereum/pull/27720)Client.Unsubscribe(https://github.com/ethereum/go-ethereum/pull/30318)Misc
contracttype parameters (https://github.com/ethereum/go-ethereum/pull/30315)--devmode (https://github.com/ethereum/go-ethereum/pull/30264)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:
ethereum/client-go.v1.14.8: Rayingri (v1.14.8)Compare Source
This is a maintenance release with bug fixes only.
Command changes
evm runcommand no longer overwrites the sender account in genesis.json. (#30259)evm runnow allows configuringbaseFeePerGasin genesis.json. (#30281)Go API
core/types.Transaction.ChainIDhad a bug where it modified the signature for very large ChainID (>= 2^64). (#30157)ethclient.Client.NetworkIDnow supports values returned in hex format by the server. (#30263)ethclient/simulated.Backend.AdjustTimewas fixed to apply the correct time divison. (#30138)accounts/abi/bind.TransactOptsnow supports setting an access list for created transactions. (#30195)p2p/simulationshas been removed. (#30250)Core
eth_callstorage 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)Networking
--nat=extip:...could lead to invalid discovery packets being generated. (#30234)Build
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:
ethereum/client-go.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:
ethereum/client-go.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:
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:
ethereum/client-go.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:
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:
ethereum/client-go.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:
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:
ethereum/client-go.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
geth --devwith a custom genesis block, the genesis file must now set difficulty and terminal total difficulty to zero. (#29579)geth init, fork timestamps will now be printed correctly. (#29514)RPC
eth_feeHistorywas changed to apply a limit on the number of requested percentiles (#29644)eth_createAccessListnow honors request cancellation and terminates background work (#29686)eth_estimateGastakes tx blobs into account for low-balance scenarios (#29703)Tracing
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:
ethereum/client-go.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
geth --devwith a custom genesis block, the genesis file must now set difficulty and terminal total difficulty to zero. (#29579)geth init, fork timestamps will now be printed correctly. (#29514)RPC
eth_feeHistorywas changed to apply a limit on the number of requested percentiles (#29644)eth_createAccessListnow honors request cancellation and terminates background work (#29686)eth_estimateGastakes tx blobs into account for low-balance scenarios (#29703)Tracing
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:
ethereum/client-go.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
hashmode topathmode (i.e.--state.schemeflipped formhashtopath) (#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 topathdb. The main advantage is built-in, online historical state pruning; no more runaway state growth.--state.scheme=hashfor now. That said, we will be droppinghashmode sooner rather than later, so we advise everyone running full nodes to gradually switch, if they haven't yet.pathmode, so archive nodes will still run inhashmode. Naturally, hash mode will not be dropped until a fullpatharchive 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.
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).
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.
terminalTotalDifficultyPassed: truefield in theirgenesis.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.
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).blsyncexecutable 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.apiflag, 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
geth db inspect-historycommand to inspect pathdb state history (#29267).libusbtohidfor simpler hardware wallet support (#28945, #29175, #29176).prestateTrancerto take into account 4844 blobs and their fees (#29168).ethclientandgethclientpackages with support for 4844 blob fields (#29198).--metrics.expensive(#29191).log/slogpackage instead ofgolang/exp(#29302).kilictognark(#29441).pebbleis overloaded (#29478).eth_blobBaseFeeRPC method, extendeth_feeHistorywith blobs (#29140).Bugfixes
geth dumpandgeth snapshot dump(#29100).devp2pcommand to not ignore specified bootnodes (#29091).prestateTracerto return the correct nonce for contract creations (#29099).devp2pcommand (#29257).hashdbmode (#29341).GetClientVersion(#29351).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:
ethereum/client-go.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:
ethereum/client-go.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:
This release is NOT critical for the Cancun fork, but recommended to make Geth lighter in anticipation to unknown blob load.
Other fixes:
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.