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.

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 module github.com/ethereum/go-ethereum to v1.12.2 - autoclosed #86

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 20, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/ethereum/go-ethereum require minor v1.11.5 -> v1.12.2

Release Notes

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

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:

  • A crash related to leveldb metrics is resolved (#​27904)
  • Metrics names used by the blobpool have been changed to be compatible with Prometheus (#​27901)
  • The c-kzg-4844 and blst libraries have been updated, hopefully fixing some build issues (#​27890, #​27907, #​27910)
  • We have also adapted go-ethereum to the latest changes in the 'slices' package provided by the golang.org/x/exp module. The Go authors decided to push an incompatible update, but didn't create a new release of that module, causing build issues when consumers mix-and-match dependency versions. (#​27909)

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


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

v1.12.1: Antibaar (v1.12.1)

Compare Source

Geth v1.12.1 is a maintenance release, albeit a rather large one, since we haven't put out a version since May.
This release is a recommended upgrade for all users and contains security-related fixes.

Here's the list of changes:

Cancun fork

Development for the upcoming Cancun hard fork has been a focus in this release cycle. Do note however, that Geth v1.12.1 is not yet ready for Cancun.

Geth command changes
  • The Rinkeby testnet is no longer supported in Geth (#​27406)
  • geth --dev now simulates a PoS-based chain (#​27327)
  • evm blocktest can now output structured logs (#​27396)
  • Geth will now configure GOMAXPROCS based on CPU quota settings. This should improve efficiency when running in Docker containers with a CPU core limit applied. (#​27506, #​27814)
  • An IPv6 listening address for can now be configured for HTTP/WS (#​27628) (#​27635)
RPC/GraphQL API changes
  • JSON transactions now have a yParity fields, as mandated by the RPC API spec (#​27744, #​27882)
  • Legacy transactions now have a chainID field in RPC responses, like all other transaction types (#​27452)
  • Block headers returned by RPC no longer report a non-standard size field (#​27347)
  • eth_estimateGas now supports state overrides like eth_call (#​27845)
  • eth_estimateGas now handles internal chain reorgs more correctly (#​27505)
  • eth_getProof is slight more efficient, and will now return a response in the canonical encoding even for off-spec input parameters (#​27309, #​27310)
  • eth_getTransactionReceipt now returns null when the transaction is not available. It used return an error in that case. (#​27712)
  • debug_storageRangeAt now takes a block hash or number as parameter (#​27328)
  • The new debug_getTrieFlushInterval method reports the internal state saving interval (#​27303)
  • A crash in the prestate tracer is resolved (#​27691)
  • Structured EVM logs returned by tracing now contain the returnData (#​27704)
  • GraphQL now supports withdrawals (EIP-4895) (#​27072)
Go library changes
  • The RPC server now enforces limits on batch requests and responses. This is a potentially breaking change.
    If you use batch requests with geth, and also use the go-ethereum RPC client library, we strongly recommend updating your go-ethereum library dependency as well. The new client version handles invalid batch responses way better than before. (#​26681)
  • The RPC client has multiple new ways to test whether the transport supports real time subscriptions (#​25942)
  • fsync is now enabled for pebble database writes (#​27615, #​27522)
  • Function calls timed by metrics will now run even if metrics are disabled (#​27724, #​27723)
  • Node.Attach no longer returns an error. This is a breaking Go API change. (#​27450)
  • The keystore has improved verification of keys loaded from disk (#​27432)
  • Per-level metrics are now available for LevelDB (#​27643)
Core
  • All block creation activity is now paused while the node is syncing (#​27218)
  • Two minor bugs in the transaction pool are resolved in this release (#​27404, #​27479)
  • Geth no longer uses a 'clean cache file' to persist internal caches across restarts. While persistent cache added a small performance boost right after startup, it could cause obscure issues in certain restart scenarios. (#​27525)
  • A large portion of the new Path-Based State Storage scheme has been implemented. While it isn't active yet, we are planning to make this new storage method available in the next release. (#​25963, #​27323, #​27349, #​27428, #​27687, #​27753, #​27815)
  • As part of testing the new storage scheme, some inconsistencies in selfdestruct handling were discovered by fuzz tests and had to be fixed (#​27376, #​27339)
  • We have also made significant progress on the integration of Verkle Trees, which required changes to internal state-handling APIs (#​27000, #​27209, #​27464, #​27476, #​27544, #​27853)
Networking
  • A serious memory leak related to database writes in snap sync is fixed in this release (#​27842)
  • Large transactions (> 4kB) are no longer broadcasted to peers. This resolves a potential network congestion issue (#​27618)
  • The p2p networking layer has learned to announce alternate ports returned by UPnP/NAT-PMP (#​26359)
  • The p2p server now properly tracks all peer goroutines (#​27887)
  • Networking initialization now really disables all discovery when --nodiscover is used (#​27518)
  • Obsolete parts of the LES protocol implementation, which is currently non-functional, have been removed (#​27737)
  • Discovery bootstrap nodes will now be filtered by the netrestrict setting, like all other nodes (#​27701)
  • We now provide additional metrics around p2p dialing, making it possible to measure the efficieny of peer discovery (#​27621)
  • The downloader no longer accumulates goroutines/memory while processing reorgs (#​27397)
  • A very rare crash related to peer connection tracking is resolved (#​27665)
  • It is now possible to configure certain discovery internals for experimentation (#​27387)
Build
  • This release is built with Go 1.20.7 (#​27835, #​27708)
  • On UNIX-like OSes, package rpc no longer uses cgo (#​27447)
  • Building go-ethereum no longer fails when .DS_Store files exist in unexpected locations (#​27521)
  • On macOS, a build warning related to libusb is resolved (#​27698)
  • An obscure build issue related to the NDEBUG C macro is resolved (#​27550)

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


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

v1.12.0: Krogam DMZ (v1.12.0)

Compare Source

Geth v1.12.0 is a potentially breaking change, hence it was deemed to deserve version bump, to 1.12.

The v1.12 release family drops support for proof-of-work, and thus can not be used any more on PoW-based private chains, or as an upstream library for projects depending on ethash PoW (#​27178, #​27147).

In our GraphQL API, a breaking change is that all numeric values are now encoded as hex strings (#​26894). The internal GraphQL UI was updated to version 2.0. (#​27294).

Regarding our move from leveldb to pebble, Geth now defaults to use Pebble as a backend if no existing database is found (#​27136). If a previous LevelDB database exists Geth will keep using that, and if you must have LevelDB for some compatibility reasons, you can force it in Geth with the --db.engine=leveldb flag.

We have made progress on "EIP-4844: Shard Blob Transactions" (#​27257, #​27256, #​27155, #​27049), beacon light sync (#​27292), and path-based state storage (#​27176, #​26813) but neither is finished as of yet.

Other improvements:

  • Add block overrides to eth_call (#​26414)
  • Make batched state-test execution possible (#​27318)

Assorted bugfixes:

  • Do not ignore null address while iterative dump (#​27320)
  • Fix flatCallTracer crasher (#​27304)
  • Prevent pebble shutdown-panic (#​27238)
  • Make websocket use default "HTTP_PROXY" by default (#​27264)
  • Make eth_estimateGas use latest block by default (#​24363)
  • Add txHash field on txTraceResult (#​27183)
  • Fix crash on querying finalized block (#​27162)

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


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

v1.11.6: Azimir (v1.11.6)

Compare Source

Geth v1.11.6 is a maintenance release, fixing some minor issues and adding some log management features.

Log management

Log rotation has landed in geth, via (#​26843). Log rotation can be activated using the flag --log.rotate. Additional parameters that can be given are:

  • --log.maxsize to set maximum size before files are rotated,
  • --log.maxbackups to set how many files are retailed,
  • --log.maxage to configure max age of rotated files,
  • --log.compress whether to compress rotated files

The location the logfile(s) can be configured as previously, using the --log.logfile parameter.

A new log output format, logfmt was added (#​27001, #​26970). It can be enabled using --log.format, which currently supports the options json, logfmt or terminal. (Thus, the --log.json option is now deprecated).

And finally, the flag --vmodule was renamed to --log.vmodule (#​27071).

Assorted

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


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


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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.11.6 fix(deps): update module github.com/ethereum/go-ethereum to v1.12.0 May 25, 2023
@renovate renovate bot force-pushed the renovate/github.51.al-ethereum-go-ethereum-1.x branch from e3e796f to f7093ba Compare May 25, 2023 12:45
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.12.0 fix(deps): update module github.com/ethereum/go-ethereum to v1.12.1 Aug 10, 2023
@renovate renovate bot force-pushed the renovate/github.51.al-ethereum-go-ethereum-1.x branch from f7093ba to 4c7dd80 Compare August 10, 2023 13:12
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.12.1 fix(deps): update module github.com/ethereum/go-ethereum to v1.12.2 Aug 12, 2023
@renovate renovate bot force-pushed the renovate/github.51.al-ethereum-go-ethereum-1.x branch from 4c7dd80 to d6935fc Compare August 12, 2023 13:47
@renovate renovate bot changed the title fix(deps): update module github.com/ethereum/go-ethereum to v1.12.2 fix(deps): update module github.com/ethereum/go-ethereum to v1.12.2 - autoclosed Sep 6, 2023
@renovate renovate bot closed this Sep 6, 2023
@renovate renovate bot deleted the renovate/github.51.al-ethereum-go-ethereum-1.x branch September 6, 2023 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants