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
Open
ethpandaops-renovatebot
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
March 21, 2023 18:24
ee047d6
to
0172338
Compare
ethpandaops-renovatebot
bot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.2
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.3
Mar 21, 2023
ethpandaops-renovatebot
bot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.3
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.4
Mar 25, 2023
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
March 25, 2023 00:55
0172338
to
78dd0a5
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
April 4, 2023 12:27
78dd0a5
to
19148fb
Compare
ethpandaops-renovatebot
bot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.4
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.5
Apr 4, 2023
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
April 6, 2023 00:52
19148fb
to
855cf35
Compare
ethpandaops-renovatebot
bot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.11.5
fix(deps): update all minor
Apr 6, 2023
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
April 6, 2023 06:22
855cf35
to
17d2321
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
April 27, 2023 12:27
390c1c8
to
759a109
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
May 4, 2023 18:21
759a109
to
6ccf234
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
May 17, 2023 12:27
6ccf234
to
b3be2aa
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
June 8, 2023 12:29
e93e6fb
to
6506fa0
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
July 4, 2023 01:38
6506fa0
to
1ff6bc5
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
July 18, 2023 01:58
1ff6bc5
to
f01adfe
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
August 1, 2023 01:30
f01adfe
to
764da61
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
August 15, 2023 01:06
764da61
to
964c56a
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
September 5, 2023 01:08
30d85fa
to
9df41f4
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
September 12, 2023 01:07
9df41f4
to
77bcd90
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
October 3, 2023 01:10
77bcd90
to
c133142
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
October 24, 2023 01:10
5a8a075
to
be7e1e1
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
October 31, 2023 01:10
be7e1e1
to
4cc00c6
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
November 14, 2023 01:11
4cc00c6
to
d8681e6
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
November 21, 2023 01:15
d8681e6
to
d40f694
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
December 5, 2023 01:16
d40f694
to
f57ed2d
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
December 26, 2023 01:11
f57ed2d
to
9908322
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
January 9, 2024 01:15
8681a90
to
8aff414
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
January 23, 2024 01:15
4b66592
to
5a247eb
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
January 30, 2024 01:13
5a247eb
to
6cdc077
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
February 20, 2024 01:09
aa30662
to
710d6a5
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
February 27, 2024 01:10
710d6a5
to
5ee8928
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
March 12, 2024 01:10
5ee8928
to
3888ddf
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
March 19, 2024 01:18
3888ddf
to
7c448f5
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
April 16, 2024 01:11
7c448f5
to
a81e255
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
May 7, 2024 01:11
a81e255
to
8eeebea
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
May 14, 2024 01:14
8eeebea
to
d1e3bc2
Compare
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.10.26
->v1.14.0
v1.14.3
(+1)v0.34.0
->v0.35.1
v0.36.0
v1.1.1
->v1.2.0
v1.16.0
->v1.19.0
v1.19.1
v1.6.1
->v1.8.0
1.20
->1.22
Release Notes
ethereum/go-ethereum (github.com/ethereum/go-ethereum)
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:
ethereum/client-go
.v1.13.5
: Carbonaceous (v1.13.5)Compare Source
Geth v1.13.5 is a scheduled maintenance release fixing a potential data corruption in path scheme which could occur due to a power failure (i.e. entire OS / machine crash).
ethclient
and thesimulated
backend to alloweth_call
against specific block hashes (#28084).And bugfixes:
For a full rundown of the changes please consult the Geth 1.13.5 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.4
: Archanes (v1.13.4)Compare Source
Geth v1.13.4 is a non-urgent hotfix release. The previous version of Geth (v1.13.3) introduced a warning log for bad transaction announcements, and on mainnet it generated too much logging noise due to a protocol violation in Erigon. To prevent overwhelming logging systems, Geth v1.13.4 lower the log to a more reasonable level until the bug in Erigon is fixed #28356.
Apart from the above reason, the release contains:
For a full rundown of the changes please consult the Geth 1.13.4 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.3
: Armeni (v1.13.3)Compare Source
Geth v1.13.3 is a scheduled maintenance release with various small additions and an important Pebble database fix.
--synctarget
(#28209).eth/66
(Cancun will requireeth/68
anyway) (#28239).snap
missingeth
protocol warning to debug level (#28249).eth/68
(#28261).Features related to the Cancun hardfork:
BLOBFEE
opcode for the upcoming Cancun hard fork (#28098).For a full rundown of the changes please consult the Geth 1.13.3 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.2
: Phaistos (v1.13.2)Compare Source
Geth v1.13.2 is a bugfix release for the 1.13 family as well as contains the Holesky testnet relaunch.
Note, if you have previously ran Geth with the old Holesky testnet configs, the new version will probably fail to start with a genesis hash mismatch error. You will need to manually delete your
holesky/chaindata
folder and restart. Geth did not implement special code for cleaning up the failed launch of the testnet.block
parameter ineth_call
optional, defaulting tolatest
(#28165).ethclient
retrieving block receipts (#28087).--bootnodes
flag if the list is also configured in the toml file (#28095).For a full rundown of the changes please consult the Geth 1.13.2 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.1
: Zakros (v1.13.1)Compare Source
Geth v1.13.1 is a hotfix release for v1.13.0.
It fixes the following issues:
path
scheme caused by a weirdly restarted snap sync (#28124, #28126).geth db inspect
command running against oldhash
scheme databases (#28108).Apart from the fixes, v1.13.1 introduces support for configuring Geth via environmental variables (#28103, #28119)!
For a full rundown of the changes please consult the Geth 1.13.1 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.13.0
: Therum (v1.13.0)Compare Source
Geth v1.13.0 is a major milestone in the lifetime of Geth, bits and bobs being in development for around 6 years now. Since a release note cannot do it justice, please see our Geth v1.13.0 release blog post.
Still, just to quickly recap, Geth v1.13.0 finally ships a new database model which supports proper, full pruning of historical states; meaning you will never need to take your node offline again to resync or to manually prune. The new database model is optional for now (you need to enable it via
--state.scheme=path
) and does require resyncing the state, since we need to store it completely different (you can keep your ancients, no need to resync the chain too).The path database will become the default eventually, but for safety reasons, we're keeping it opt-in for the moment. The old database model is not going away soon, though long term - unless there's something fundamentally wrong with the path db - it will. As for archive node users, we're working on a new model there too, but it does need a bit more work on top, so that's for another release.
The all important disclaimer: Geth's new path-based storage is considered stable and production ready, but was obviously not battle tested yet outside of the team. Everyone is welcome to use it, but if you have significant risks if your node crashes or goes out of consensus, you might want to wait a bit to see if anyone with a lower risk profile hits any issues.
Apart from the pruning work, the release contains:
eth_estimateGas
to do fewer runs (#27710).eth_getBlockReceipts
RPC API call (#27702).And bugfixes:
--dev
) mode (#27886).For a full rundown of the changes please consult the Geth 1.13.0 release milestone, though do note that the state scheme changes and pruner have been gradually merged over the past year so are not explicitly tagged in this milestone.
As with all our previous releases, you can find the:
ethereum/client-go
.v1.12.2
: Mawinor (v1.12.2)Compare Source
Hot on the heels of v1.12.1 comes our next release, fixing some regressions reported by the community.
Here are the changes:
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.