fix(deps): update all non-major golang dependencies - autoclosed#25
Closed
renovate[bot] wants to merge 1 commit into
Closed
fix(deps): update all non-major golang dependencies - autoclosed#25renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
bd706b0 to
e78a455
Compare
c4d58b6 to
49efbe2
Compare
0f76946 to
b23152d
Compare
31f7283 to
7973cb6
Compare
6362582 to
ecb787d
Compare
ecb787d to
0318bc3
Compare
7c89f89 to
034f073
Compare
0f09570 to
c37e59d
Compare
07145d8 to
d666aa4
Compare
4571219 to
c7b56b8
Compare
f0e7af6 to
e90755c
Compare
0feb260 to
4eeebd4
Compare
8ddff83 to
1b2cad0
Compare
1b2cad0 to
dedc4f3
Compare
d78f307 to
b3c10bf
Compare
321e1bd to
e8f4e1a
Compare
0018a6d to
1262329
Compare
1262329 to
5c14610
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
This file contains hidden or 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
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.20.0->v1.36.3v1.18.32->v1.29.14v1.24.1->v1.38.3v1.12.0->v1.15.11Release Notes
aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)
v1.36.3Compare Source
v1.36.2Compare Source
v1.36.1Compare Source
v1.36.0Compare Source
v1.35.0Compare Source
v1.34.0Compare Source
v1.33.0Compare Source
v1.32.8Compare Source
v1.32.7Compare Source
v1.32.6Compare Source
v1.32.5Compare Source
v1.32.4Compare Source
v1.32.3Compare Source
v1.32.2Compare Source
v1.32.1Compare Source
ethereum/go-ethereum (github.com/ethereum/go-ethereum)
v1.15.11: Armored Compartments (v1.15.11)Compare Source
This is a maintenance release, correcting issues with log and transaction indexing. Upgrading to this release is not required to follow the Pectra fork on mainnet, you can keep using v1.15.9 or v1.15.10, but we recommend you upgrade at your convenience to fix RPC issues.
All changes
eth_getTransactionByHashis resolved. (#31752)eth_simulateV1now correctly returns the transaction sender (from). (#31480)eth_estimateGasrelated tofloorDataGasis resolved. (#31735)ethclient'sBlockByNumbercan now retrieve the pending block. (#31504)geth initwill once again exit in error when trying to re-initialize a database with an incompatible config. (#31743)geth --devmode is resolved. (#31758)For a full rundown of the changes please consult the Geth 1.15.11 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.10: Omni-Capacitors (v1.15.10)Compare Source
This is a bug-fix release that corrects an issue with the new log indexer and configures the beacon chain light client for the Electra fork on mainnet (we forgot about this in v1.15.9).
This release is also suitable for following the Pectra fork on Mainnet.
All changes
authorizationListto calls. (#31198)debug_setMemoryLimithas been added for tweaking Go garbage collector behavior. We do not recommended using this, it's just a facility for debugging Geth. (#31441)For a full rundown of the changes please consult the Geth 1.15.10 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.9: Multicapacitor (v1.15.9)Compare Source
This release enables the Prague execution-layer fork on mainnet.
Prague
As of this release, the Prague fork is scheduled to occur on mainnet at block timestamp
1746612311(Wed May 07 10:05:11 2025 UTC). As a reminder, the fork contains the following EIPs:MAX_EFFECTIVE_BALANCEAll changes
eth_sendRawTransactionwould always return a txhash, even if the transaction wasn't includable on chain. (#31618)eth_feeHistoryrelated to blob fees is resolved. (#31663)For a full rundown of the changes please consult the Geth 1.15.9 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.8: Combatives Upgrade (v1.15.8)Compare Source
This is a bug-fix release with some performance improvements.
Geth
geth importnow applies database and cache flags correctly. (#31577, #31534)blsyncnow has a feature to export checkpoint files. (#31469)Core library
fsynca while ago to improve performance on slow filesystems, but it has lead to reports of instability. The performance hit from enabling data sync is negligible. (#31519)RPC
P2P networking
*enode.Nodeto handlers. This is a breaking change, but the only known user of this API is the shisui portal network client. (#31075)skipvalues when processingGetBlockHeadersmessages from peers. This is not a security fix, despite looking like one, it's more about correctness. (#31522)Build
For a full rundown of the changes please consult the Geth 1.15.8 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.7: Juggernaut Shield (v1.15.7)Compare Source
This is a bug fix release. We are putting is out specifically to address a critical issue that could break archive node databases.
--state.scheme=hashwhere the log indexer would accidentally delete trie nodes. (#31525)ethclient/simulated.Backendis fixed in this release. (#31228)eth_createAccessListnow supports state overrides likeeth_call. (#31497)eth_createAccessListwill now exclude 7702 authorities from the result. (#31336)eth_estimateGas. (#31394)For a full rundown of the changes please consult the Geth 1.15.7 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.6: Mental Focuser (v1.15.6)Compare Source
🚧 Note: we are investigating an issue with this release that affects archive nodes (--gcmode=archive).
If you are running Geth in this mode, please hold off upgrading. 🚧
This is a feature release, with two exciting upgrades:
Log filtering in Geth receives a huge performance upgrade with the introduction of our new 'filtermaps' index. Unlike the previous 'bloombits' index, query performance no longer suffers as the density of logs in a block increases. The new index design is also a step towards a future where filtering results can be proven by the server. See the PR and associated design documents for more information.
In practical terms, the new index is a bit larger than the old one. As before, you can choose the amount of historical blocks to be indexed using the
--history.logscommand-line flag. We have adjusted the default value of this flag to cover one year of history, and the resulting index has a size of ~10GB for Ethereum mainnnet. Indexing of the entire chain with--history.logs=0will take up ~61GB.Once the index is built, searches will be fast, but note that querying outside of the indexed block range will fall back to a very slow unindexed search. We will continue optimizing log searches in future releases, and welcome your feedback and bug reports in this area. (#31065, #31079, #31080, #31081, #31419, #31429, #31450, #31463, #31455)
abigen v2 is finally here. abigen is a tool for creating Go bindings for Solidity contracts. In v1, the generated bindings presented an API for sending transactions, filtering logs, and performing read-only calls as Go methods on the contract object. In the new version, we have updated the interface of the generated code to focus purely on encoding and decoding ABI payloads. Generic helper functions are provided in a library package to enable the same interactions as before, but you can also use your own custom method of signing & sending transactions. Generated bindings are also significantly smaller. (#31379)
Other changes in this release:
RPC
eth_sendRawTransaction- where transactions with too-low nonce would be accepted by the API - has been fixed. (#31473)eth_call/estimateGasRPC methods will now always return error code 3 for reverts. It previously only returned this code when the EVM produced revert data. (#31456)eth_simulateV1now returns a correct logs bloom value in the simulated block (#31411)eth_simulateV1supports block overrides for the beacon root and withdrawals (#31304)debug_traceCall: themovePrecompileTooverride feature should now work correctly (#31348)debug_traceCalland other related RPC methods now hex-encode the EVM return value. This is a breaking change. (#31216, #31445)ethclienthas a new methodEstimateGasAtBlock(#27508)Geth
geth importnow properly handles Ctrl-C interrupts (#31360)geth --devmode will now pre-fund all precompile accounts supported by the Pectra upgrade (#31342)geth --devnow respects the--miner.pending.feeRecipientflag (#31316)Core library
For a full rundown of the changes please consult the Geth 1.15.6 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.5: Stronghold Package (v1.15.5)Compare Source
Alright 🥲 This is a hotfix release for an issue on the Sepolia testnet. Shortly after the Pectra fork activation, an issue in deposit contract logs parsing was discovered. Sepolia has a custom version of the deposit contract that also implements ERC-20, and thus unexpected log events may be created by transactions to it. This issue affects all Ethereum execution clients.
The Sepolia testnet may take a short while to recover while the update is adopted by nodes. An incident report will be published once the network has fully recovered. ❤️🩹
Other changes in this release:
debug_traceTransaction, the "memory" and "storage" fields will be omitted if empty. (#31289)For a full rundown of the changes please consult the Geth 1.15.5 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.4: Commando Package (v1.15.4)Compare Source
This is a bug fix release.
Note: you need to upgrade to v1.15.3 or this release to be compatible with the Pectra fork on the Sepolia network (activates Wed, Mar 5 at 07:29:36 UTC).
eth_feeHistorythat caused incorrectblobGasRatioreturn values. (#31246, #31270)BlobBaseFeemethod to request the current blob basefee. (#31290)For a full rundown of the changes please consult the Geth 1.15.4 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.3: Expert Package (v1.15.3)Compare Source
Oh look, another hotfix release! We are issuing this Geth release to correct the predefined fork configuration of the Holesky and Sepolia testnets. The deposit contract address was missing in the configuration for these networks, causing a chain validation failure.
This issue was discovered on the Holesky network after it had already forked into Pectra (Prague). As a reminder, the Sepolia network will fork to Pectra at slot
7118848(Wed, Mar 5 at 07:29:36 UTC). You need to upgrade to Geth v1.15.3 until then in order to use the testnet after the fork.All changes in this release:
eth_simulateV1RPC method was improved to match regular block processing semantics. (#31176, #31122)--discovery.dnsflag value will now cause an error at Geth startup. (#31233)--devmode can now handle custom genesis configs with forks older than the latest. (#31084)core/asm) has been removed. (#31211)For a full rundown of the changes please consult the Geth 1.15.3 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.2: Survivor Loadout (v1.15.2)Compare Source
This release fixes a few regressions. In particular, it restores block building on mainnet, which was broken in v1.15.1.
Note: a regression in the Prague fork implementation was discovered and fixed in a follow-up release. Please upgrade to at least v1.15.3 to follow the fork.
All changes in this release:
geth dumpconfigrelated to theP2P.NATsetting in TOML is fixed. (#31192)For a full rundown of the changes please consult the Geth 1.15.2 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.1: Engineering Kit (v1.15.1)Compare Source
This release enables the Prague fork for the Holesky and Sepolia testnets. It is a required upgrade if you want to participate in these networks.
Note: a regression in the Prague fork implementation was discovered and fixed in a follow-up release. Please upgrade to at least v1.15.3 to follow the fork.
The fork is set to activate at
3710976, timestamp: Mon, Feb 24 at 21:55:12 UTC7118848, timestamp: Wed, Mar 5 at 07:29:36 UTCOther user-facing changes in this release:
blobSchedulesetting. Geth v1.15.1 has been updated no longer crash in this case, and we will have an improved fix in v1.15.2 (#31171)evmcommand related to state dumps has been fixed. (#31158)debug_getRaw*RPC methods has been fixed. (#31157)For a full rundown of the changes please consult the Geth 1.15.1 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.15.0: Operative Package (v1.15.0)Compare Source
We are proud to announce the Geth 1.15.0 release.
This release contains some breaking changes to the database. Downgrading to v1.14.x requires re-syncing the chain.
Prague Fork
As of this release, Geth implements the Prague fork specifications up to devnet-6.
Command changes
evmcommand has seen lots of updates, improving its command-line interface and internals. (#30633, #30849, #30806, #30927, #30780, #30854, #31055, #30805, #30804, )--metricsflag. (#30814)--natflag) with the config file. (#31041)geth --traceflag is now called--go-execution-traceto avoid confusion with EVM tracing. (#30846)bootnodeutility has been removed. (#30813)RPC & Tracing
eth_estimateGasnow supports block overrides likeeth_call. (#30695)eth_simulateV1now advances the timestamp by 12 seconds per block. (#30981)accounts/abinow supports unpacking Solidity error types. (#30738)accounts/abi/bindhas new functionsWaitMinedHash,WaitDeployedHash. (#30079)accounts/usbwalletwas updated to support new Ledger firmware and the Ledger Flex device. (#31004)ethclient/simulated, a bug was fixed where transactions couldn't be sent afterRollbackof the simulated chain. (#31020)Database
This release introduces a new database schema version. A downgrade to v1.14.x requires a resync.
Core Library & Networking
The fix for CVE-2025-24883 (recent v1.14.13 hotfix release) is also in v1.15.0 (#31100).
The transaction pool's notion of "locals" has been changed. This is a breaking change in some ways, and requires some explanation. Geth used to accept transactions at any fee level via RPC, storing them into the node's pool, and marking the sender as "local". When creating a new block (or the pending block), it would choose "local" transactions first. Finally, Geth tracks "local" transactions in a persistent journal file, and restores them on startup. The effect of all this is that once you had sent a transaction to Geth via RPC, it would keep prioritizing the sender account and its transactions (even ones received through p2p).
In Geth v1.15, we are changing this model to a different one. When receiving a transaction via RPC, it is stored into the pool like any other transaction, but it is also inserted into a separate "locals tracker" that keeps reinjecting the tx into the main pool periodically. When building a block, Geth no longer prefers the txpool locals, but you can configure a set of addresses that should get priority using the
--txpool.localsCLI flag. (#30559, #31127)For static nodes (from configuration or RPC
admin_addPeer), the node URL can contain a DNS name. Geth will now resolve these names when attempting to connect to the peer, instead of at configuration parsing time. This is useful for setting up testing networks in Docker or Kubernetes where the IP address of a node might not be known ahead of time. (#30822)Geth can now use the STUN protocol to figure out its own IP. There is a built-in list of public servers, or you can specify your own. Use
--nat=stunto enable. (#31064)Some minor bugs in the p2p protocol implementation got fixed. (#30855, #30918)
Build
For a full rundown of the changes please consult the Geth 1.15.0 release milestone
As with all our previous releases, you can find the:
ethereum/client-go.v1.14.13: Schwarzschild (v1.14.13)Compare Source
This is a security release, fixing a vulnerability (CVE-2025-24883).
Please update your nodes ASAP.
As with all our previous releases, you can find the:
ethereum/client-go.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 rundo
Configuration
📅 Schedule: Branch creation - "every 1 months on the first day of the month" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.