-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
fix(deps): update all minor #77
base: main
Are you sure you want to change the base?
Conversation
ee047d6
to
0172338
Compare
0172338
to
78dd0a5
Compare
78dd0a5
to
19148fb
Compare
19148fb
to
855cf35
Compare
855cf35
to
17d2321
Compare
390c1c8
to
759a109
Compare
759a109
to
6ccf234
Compare
6ccf234
to
b3be2aa
Compare
e93e6fb
to
6506fa0
Compare
6506fa0
to
1ff6bc5
Compare
1ff6bc5
to
f01adfe
Compare
f01adfe
to
764da61
Compare
764da61
to
964c56a
Compare
30d85fa
to
9df41f4
Compare
9df41f4
to
77bcd90
Compare
77bcd90
to
c133142
Compare
5a8a075
to
be7e1e1
Compare
be7e1e1
to
4cc00c6
Compare
4cc00c6
to
d8681e6
Compare
d8681e6
to
d40f694
Compare
d40f694
to
f57ed2d
Compare
f57ed2d
to
9908322
Compare
8681a90
to
8aff414
Compare
4b66592
to
5a247eb
Compare
5a247eb
to
6cdc077
Compare
aa30662
to
710d6a5
Compare
710d6a5
to
5ee8928
Compare
5ee8928
to
3888ddf
Compare
3888ddf
to
7c448f5
Compare
7c448f5
to
a81e255
Compare
a81e255
to
8eeebea
Compare
8eeebea
to
d1e3bc2
Compare
d1e3bc2
to
089056a
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
089056a
to
18cd105
Compare
18cd105
to
12682da
Compare
12682da
to
6cbe8f2
Compare
6cbe8f2
to
aea90df
Compare
aea90df
to
0b43340
Compare
0b43340
to
aa455d8
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
v1.10.26
->v1.14.7
v1.14.8
v0.34.0
->v0.38.0
v0.39.0
v1.1.1
->v1.2.0
v1.16.0
->v1.19.1
v1.6.1
->v1.8.1
Release Notes
ethereum/go-ethereum (github.com/ethereum/go-ethereum)
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 --dev
with 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_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
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 --dev
with 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_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
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
hash
mode topath
mode (i.e.--state.scheme
flipped formhash
topath
) (#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=hash
for now. That said, we will be droppinghash
mode sooner rather than later, so we advise everyone running full nodes to gradually switch, if they haven't yet.path
mode, so archive nodes will still run inhash
mode. Naturally, hash mode will not be dropped until a fullpath
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.
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: true
field 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).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
geth db inspect-history
command to inspect pathdb state history (#29267).libusb
tohid
for simpler hardware wallet support (#28945, #29175, #29176).prestateTrancer
to take into account 4844 blobs and their fees (#29168).ethclient
andgethclient
packages with support for 4844 blob fields (#29198).--metrics.expensive
(#29191).log/slog
package instead ofgolang/exp
(#29302).kilic
tognark
(#29441).pebble
is overloaded (#29478).eth_blobBaseFee
RPC method, extendeth_feeHistory
with blobs (#29140).Bugfixes
geth dump
andgeth snapshot dump
(#29100).devp2p
command to not ignore specified bootnodes (#29091).prestateTracer
to return the correct nonce for contract creations (#29099).devp2p
command (#29257).hashdb
mode (#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:
eth_createAccessList
if--gascap=0
(#28846).For a full rundown of the changes please consult the Geth 1.13.14 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.13
: Alsages (v1.13.13)Compare Source
This is a minor release with fixes for several issues related to the upcoming Cancun mainnet fork. As such, it is recommended for all mainnet users.
Changes in this release:
eth_fillTransaction
has seen some bug fixes related to blob transactions as well. (#28929, #29037)getClientVersionV1
on the Engine API endpoint. (#28915, #28994)Go API changes:
ethereum.CallMsg
now contains EIP-4844 related fields (#28989)core.GenesisAlloc
is now available from packagecore/types
. We hope this change will reduce external dependencies on packagecore
. (#29003)For a full rundown of the changes please consult the Geth 1.13.13 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.12
: Edolus (v1.13.12)Compare Source
This release embeds the mainnet fork number for Cancun, scheduled to go live on 13th March, 2024 (unix
1710338135
). The specification can be read here, and it contains the following changes:To go along Cancun, we're providing refreshed Grafana dashboards:
Other than that, the following assorted fixes and features are included in this release:
era
format. Theera
format is meant to provide a cross-client archive formatfor block data (#26621, #28959)
For a full rundown of the changes please consult the Geth 1.13.12 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.11
: Tremanre (v1.13.11)Compare Source
This release fixes a few bugs and enables the Cancun upgrade for the Sepolia and Holesky networks; Sepolia will upgrade on Jan 31, and Holesky on Feb 7, and naturally this is a required upgrade if you intend to follow either chain.
eth_syncing
is slightly changed, so that it nowdoes reports
true
until transaction indexing is finished. (#28703)rlpdump
: add-pos
flag for displaying byte positions (#28785)For a full rundown of the changes please consult the Geth 1.13.11 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.10
: Sharjila B (v1.13.10)Compare Source
This release is equivalent to v1.13.9, just contains a version bump. The reason is that a bad commit was tagged on 1.13.9 originally and whilst it was untagged and fixed, some caches (Go's package manager (
go mod
)) managed to store the temporary bad version. As there is no way for us to flush the bad version out, it's cleaner to tag a next version instead. Apologies about the mess.This release fixes a few issues and enables the Cancun upgrade for the Goerli network at block timestamp
1705473
(#28719) which is 6:32:am 17. Jan. 2024 UTC.Apart from the Goerli configuration update, we have a few other changes.
accounts/abi/backends
was rewritten. The improved version is available from the new packageethclient/simulated
. A backwards-compatibility wrapper remains in the old location. (#28202)"error"
. (#28774, #28780)log
for consumers of the geth library (#28747)geth removedb
can now be run non-interactively (#28725)Testing
currentExcessBlobGas
to the state tests for better coverage of state tests (#28735)For a full rundown of the changes please consult the Geth 1.13.9 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.9
: Sharjila (v1.13.9)Compare Source
This release fixes a few issues and enables the Cancun upgrade for the Goerli network at block timestamp
1705473
(#28719) which is 6:32:am 17. Jan. 2024 UTC.Apart from the Goerli configuration update, we have a few other changes.
accounts/abi/backends
was rewritten. The improved version is available from the new packageethclient/simulated
. A backwards-compatibility wrapper remains in the old location. (#28202)"error"
. (#28774, #28780)log
for consumers of the geth library (#28747)geth removedb
can now be run non-interactively (#28725)Testing
currentExcessBlobGas
to the state tests for better coverage of state tests (#28735)For a full rundown of the changes please consult the Geth 1.13.9 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.8
: Patavig (v1.13.8)Compare Source
This is a hotfix release for a regression which affects v1.13.6 and v1.13.7: if the node is shut down during sync, the node will refuse to start, with the error message
Fatal: Failed to register the Ethereum service: waiting for sync
(#28718, #28724).Please also see the release notes for v1.13.6 and v1.13.7
For a full rundown of the changes please consult the Geth 1.13.8 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.7
: Fargeluse (v1.13.7)Compare Source
We're issuing this release to fix an issue with our build pipeline. There are also some other changes:
eth_sendTransaction
RPC method now behaves more correctly for low-fee transactions. (#27834)For a full rundown of the changes please consult the Geth 1.13.7 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.6
: Porolan (v1.13.6)Compare Source
Geth v1.13.6 is a scheduled maintenance release, but it also contains some changes which might affect node operators, concerning logging.
Gas estimation changes
The gas estimator was heavily reworked (#28600, #28618). The new version runs quite a bit faster (normally completing in 7-8 attempts rather than 18-20). However, the results have an error ratio of
1.5%
, and the estimation outcome won't always be deterministic.Logging changes
In the absence of an 'official' Go logging framework, go-ethereum has, for a very long time, used a custom in-house logger. However, just such an 'official' Go logging framework has now arrived, with the
slog
package.As of
v1.13.6
, geth now usesslog
, which will affect Geth users in different ways.Main changes are as follows:
--verbosity
and--vmodule
options.--log.backtraceat
and--log.debug
are removed.log.Format
and the methodlog.FormatFunc
,TerminalHandler.TerminalFormat
formatting methods (renamed toTerminalHandler.format
)log.Lazy
valuesThe external-facing API is largely the same as the existing Geth logger. Method signatures remain unchanged. A small semantic difference is that a
Handler
can only be set once perLogger
and not changed dynamically. This just means that a new logger must be instantiated every time the handler of the root logger is changed.For users of the
github.com/ethereum/go-ethereum/log
package: If you were using this package for your own project, you will need to change the initialization. If you previously didYou now instead need to do
The lazy handler was useful in the old log package, since it could defer the evaluation of costly attributes until later in the log pipeline. Thus, if the logging was done at 'Trace', we could skip evaluation if logging only was set to 'Info'. With the move to slog, this way of deferring evaluation is no longer needed, since slog introduced 'Enabled'. Thus the caller can do the evaluate-or-not decision at the callsite, which is much more straight-forward than dealing with lazy reflect-based evaluation.
See more about reasoning here: https://github.com/ethereum/go-ethereum/issues/28558#issuecomment-1820606613
More detailed information can be found in the PRs #28187, #28621, #28622 )
Other changes
ns/µs
mismatch in metrics for rpc-methods (#28649)HTTPHost
,WSHost
flags (#28669)evm t8n
support custom tracers (#28557)For a full rundown of the changes please consult the Geth 1.13.6 release milestone.
As with all our previous releases, you can find the:
Configuration
📅 Schedule: Branch creation - "every 2 weeks on Tuesday" in timezone Europe/Berlin, Automerge - "after 9am every weekday except Friday or Monday,before 11am every weekday except Friday or Monday" in timezone Europe/Berlin.
🚦 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.