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 #134
Open
ethpandaops-renovatebot
wants to merge
1
commit into
master
Choose a base branch
from
renovate/all-minor
base: master
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
June 7, 2023 12:26
0026f16
to
7cb1f98
Compare
ethpandaops-renovatebot
bot
changed the title
chore(deps): update golang docker tag to v1.20
fix(deps): update all minor
Jun 7, 2023
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
4 times, most recently
from
June 13, 2023 18:21
470b392
to
4a6f736
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
3 times, most recently
from
June 19, 2023 06:28
b80ec35
to
fd3b0c4
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
June 27, 2023 01:39
61983c7
to
e8bdc5b
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
July 11, 2023 01:32
202583d
to
7e19fea
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
July 25, 2023 01:33
ccf60c1
to
10f569b
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
August 8, 2023 01:19
cc0adf4
to
f6d0870
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
August 15, 2023 01:08
f6d0870
to
34739ad
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
August 22, 2023 01:11
34739ad
to
c250c60
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
September 5, 2023 01:10
eba3439
to
4b55aa2
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
September 12, 2023 01:09
4b55aa2
to
8987cbf
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
September 19, 2023 01:13
8987cbf
to
4654cbf
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
October 3, 2023 01:12
bf4afdf
to
30c1133
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
October 17, 2023 01:12
fb08aa5
to
149d064
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
October 24, 2023 01:12
149d064
to
5287cc7
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
October 31, 2023 01:12
5287cc7
to
aa3cfa6
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
November 14, 2023 01:13
aa3cfa6
to
79304b5
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
November 21, 2023 01:17
79304b5
to
6a3cc82
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
November 28, 2023 01:17
6a3cc82
to
13b2035
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
December 12, 2023 01:15
41a4813
to
1a97575
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
December 26, 2023 01:13
1a97575
to
de0e148
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
January 9, 2024 01:17
f78b714
to
ba17082
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
January 23, 2024 01:17
70861c1
to
dd1ad63
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
January 30, 2024 01:15
dd1ad63
to
9d5144f
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
February 20, 2024 01:10
aa6c8b8
to
79511a9
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
March 5, 2024 01:10
c5a5a73
to
fb6e004
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
March 12, 2024 01:12
fb6e004
to
790e4ae
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
March 26, 2024 01:14
d37ada9
to
e259406
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
April 2, 2024 01:17
e259406
to
8f1fff2
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
April 16, 2024 01:13
8f1fff2
to
51eb2ae
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
2 times, most recently
from
April 30, 2024 01:13
226f50a
to
a17eb71
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
May 7, 2024 01:13
a17eb71
to
76ef5c5
Compare
ethpandaops-renovatebot
bot
force-pushed
the
renovate/all-minor
branch
from
May 14, 2024 01:17
76ef5c5
to
e9827d0
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:
v0.19.10
->v0.21.3
v0.21.4
v4.5.1
->v4.6.0
v4.2.1
->v4.3.0
v1.13.14
->v1.14.0
v1.14.3
(+1)v1.27.1
->v1.37.0
v1.25.0
->v1.27.1
v0.6.0
->v0.7.0
v1.62.1
->v1.63.2
v0.6.0
->v0.8.0
0.37.1-alpine
->0.38.0-alpine
0.34.1-alpine
->0.38.0-alpine
Release Notes
attestantio/go-eth2-client (github.com/attestantio/go-eth2-client)
v0.21.3
Compare Source
v0.21.2
Compare Source
v0.21.1
Compare Source
v0.21.0
Compare Source
v0.20.0
Compare Source
avast/retry-go (github.com/avast/retry-go/v4)
v4.6.0
Compare Source
What's Changed
New Contributors
Full Changelog: avast/retry-go@v4.5.1...v4.6.0
cenkalti/backoff (github.com/cenkalti/backoff/v4)
v4.3.0
Compare Source
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
.go-co-op/gocron (github.com/go-co-op/gocron)
v1.37.0
Compare Source
What's Changed
New Contributors
Full Changelog: go-co-op/gocron@v1.36.1...v1.37.0
v1.36.1
Compare Source
What's Changed
New Contributors
Full Changelog: go-co-op/gocron@v1.36.0...v1.36.1
v1.36.0
Compare Source
What's Changed
New Contributors
Full Changelog: go-co-op/gocron@v1.35.3...v1.36.0
v1.35.3
Compare Source
What's Changed
(*regexp.Regexp).MatchString
by @Juneezee in https://github.com/go-co-op/gocron/pull/602Every
return an immediate error #600 by @husam-e in https://github.com/go-co-op/gocron/pull/603New Contributors
Full Changelog: go-co-op/gocron@v1.35.2...v1.35.3
v1.35.2
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.35.1...v1.35.2
v1.35.1
Compare Source
What's Changed
New Contributors
Full Changelog: go-co-op/gocron@v1.35.0...v1.35.1
v1.35.0
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.34.2...v1.35.0
v1.34.2
Compare Source
Fixes
New Contributors
Full Changelog: go-co-op/gocron@v1.34.1...v1.34.2
v1.34.1
Compare Source
Fixes
New Contributors
Full Changelog: go-co-op/gocron@v1.34.0...v1.34.1
v1.34.0
Compare Source
What's Changed
Fixes
Chores
Full Changelog: go-co-op/gocron@v1.33.1...v1.33.2
v1.33.1
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.33.0...v1.33.1
v1.33.0
Compare Source
What's Changed
Documentation & Version Bumps
Full Changelog: go-co-op/gocron@v1.32.1...v1.33.0
v1.32.1
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.32.0...v1.32.1
v1.32.0
Compare Source
What's Changed
Swap()
andLess()
methods were removed from the scheduler. These were public methods to enable slice sorting of the jobs in the scheduler. With the change to a map, they no longer have any use or value.Full Changelog: go-co-op/gocron@v1.31.2...v1.32.0
v1.31.2
Compare Source
What's Changed
New Contributors
Full Changelog: go-co-op/gocron@v1.31.1...v1.31.2
v1.31.1
Compare Source
What's Changed
SingletonMode
jobs by @david-littlefarmer in https://github.com/go-co-op/gocron/pull/536New Contributors
Full Changelog: go-co-op/gocron@v1.31.0...v1.31.1
v1.31.0
Compare Source
What's Changed
New Contributors
Full Changelog: go-co-op/gocron@v1.30.2...v1.31.0
v1.30.2
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.30.1...v1.30.2
v1.30.1
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.30.0...v1.30.1
v1.30.0
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.29.0...v1.30.0
v1.29.0
Compare Source
What's Changed
Chores
Full Changelog: go-co-op/gocron@v1.28.3...v1.29.0
v1.28.3
Compare Source
Bug fixes
Chores
Full Changelog: go-co-op/gocron@v1.28.2...v1.28.3
v1.28.2
Compare Source
What's Changed
StartAt
by @JohnRoesler in https://github.com/go-co-op/gocron/pull/505Full Changelog: go-co-op/gocron@v1.28.1...v1.28.2
v1.28.1
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.28.0...v1.28.1
v1.28.0
Compare Source
What's Changed
Full Changelog: go-co-op/gocron@v1.27.1...v1.28.0
huandu/go-sqlbuilder (github.com/huandu/go-sqlbuilder)
v1.27.1
Compare Source
v1.27.0
: New feature: New builderWhereClause
dedicated for WHERE clauseCompare Source
Due to the importance of the
WHERE
statement in SQL, we often need to continuously append conditions and even share some commonWHERE
conditions among different builders. Therefore, we abstract theWHERE
statement into aWhereClause
struct, which can be used to create reusableWHERE
conditions.I hope the
WhereClause
can help more developers to build more and more valuable SQL/DB related packages on top of this package. It's extremely welcome!What's Changed
WhereClause
: A new dedicated builder for WHERE. Thanks for raising this idea to me in #145, @LeDuyViet.Full Changelog: huandu/go-sqlbuilder@v1.26.0...v1.27.0
v1.26.0
: New feature: Support Informix SQLCompare Source
What's Changed
Informix
. Thanks for your contribution, @zhangyongding.Full Changelog: huandu/go-sqlbuilder@v1.25.0...v1.26.0
grpc/grpc-go (google.golang.org/grpc)
v1.63.2
: Release 1.63.2Compare Source
Bugs
v1.63.1
: Release 1.63.1Compare Source
Bugs
API Changes
v1.63.0
: Release 1.63.0Compare Source
Behavior Changes
resolver.Address.String()
(experimental) (#6923)New Features
ClientConn.CanonicalTarget()
to return the canonical target string. (#7006)grpc.NewClient
to allow users to create new clients in idle mode and with "dns" as the default resolver (#7010)API Changes
ClientConn.Target()
(#7006)Bug Fixes
grpc.Server
as anhttp.Handler
with the Go stdlib HTTP server (#6989)SetResolvingTimeout
to allow configuring the DNS resolver's global timeout (#6917)v1.62.2
: Release 1.62.2Compare Source
Dependencies
guyarb/golang-test-annotations (guyarb/golang-test-annotations)
v0.8.0
Compare Source
What's Changed
New Contributors
Full Changelog: guyarb/golang-test-annotations@v0.7.0...v0.8.0
v0.7.0
: Supporting optional working directoryCompare Source
What's Changed
New Contributors
Full Changelog: guyarb/golang-test-annotations@v0.6.0...v0.7.0
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.