Skip to content

build(deps): bump the go-minor-patch group across 1 directory with 7 updates - #385

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/go-minor-patch-5d029c1834
Closed

build(deps): bump the go-minor-patch group across 1 directory with 7 updates#385
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/go-minor-patch-5d029c1834

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the go-minor-patch group with 7 updates in the / directory:

Package From To
github.com/ethpandaops/cbt 0.1.6 0.1.9
github.com/ethpandaops/tracoor 0.0.33 0.1.0
github.com/grpc-ecosystem/grpc-gateway/v2 2.30.0 2.31.0
github.com/moby/moby/api 1.56.0 1.56.1
github.com/moby/moby/client 0.6.0 0.6.1
github.com/redis/go-redis/v9 9.22.0 9.23.0
golang.org/x/sys 0.48.0 0.49.0

Updates github.com/ethpandaops/cbt from 0.1.6 to 0.1.9

Release notes

Sourced from github.com/ethpandaops/cbt's releases.

v0.1.9

Changelog

  • c3d48379f1ece921c6027cfa5f21e6c6992f85ab fix(models): add one DAG edge per dependency shared across OR groups (#165)
  • 049ee15fd818585b1be252552f26630f8cd39419 test(worker): cover empty external bounds pickup against a real ClickHouse (#164)

v0.1.8

What's Changed

Full Changelog: ethpandaops/cbt@v0.1.7...v0.1.8

v0.1.7

What's Changed

Full Changelog: ethpandaops/cbt@v0.1.6...v0.1.7

Commits
  • c3d4837 fix(models): add one DAG edge per dependency shared across OR groups (#165)
  • 049ee15 test(worker): cover empty external bounds pickup against a real ClickHouse (#...
  • 14972d5 fix(worker): run incremental external scans as full scans when cached bounds ...
  • a037487 fix(clickhouse): stop connection pool slot leaks from wedging the engine (#162)
  • 1092672 refactor: decompose monolithic packages, add sweeping test coverage, moderniz...
  • See full diff in compare view

Updates github.com/ethpandaops/tracoor from 0.0.33 to 0.1.0

Release notes

Sourced from github.com/ethpandaops/tracoor's releases.

v0.1.0

Changelog

  • 9f44ea1177b6ae84be2ccc385338881846ab61d0 Archive and promote the envelope half of a gloas slot
  • 221077f08a519d91bbba3fb9cb8b0c074d40d19b Merge branch 'master' into release/glamsterdam-devnet-7
  • bf18f8d2427b1f2b95917bdddb9d8b56b0cbee31 Merge pull request #68 from ethpandaops/feat/gloas-to-master
  • b14b7ae3946a601ff54f45f7b186128b2d2b4995 Merge remote-tracking branch 'origin/release/glamsterdam-devnet-7' into release/glamsterdam-devnet-8
  • 3efddf70ff0e573008cb8263185d571a96c653a3 Promotion service on devnet-8: merge #65, and fix what the capture pipeline moved under it (#67)
  • bc06283d8338e6d106fe2dc5c5aea16772a9fc8a Verified capture pipeline: dedup by content, stream everything, store what is distinct (#66)
  • daba6036415956a823559cd836b33186874350d4 chore(deps): move gloas support onto released dependencies
  • df1dc197679ba13621b95cc83f7366e97d7a3f18 chore(deps): patch reachable govulncheck findings
  • c66578009e93cccca24a24cc021b50ca70c8a5ba chore(deps): pin beacon to the v0.71.0 gloas release
  • 8ecaaaadf291a2c7b01bdf9eeb3f1d258e24dc97 ci: repair lint and smoke-test for the go 1.26 toolchain
  • 8ae1495224b42658829547f2b740269eb15de2a0 feat: archive signed execution payload envelopes (gloas)
  • b281d6781c5058b389f58057a3fdd22adbbb8213 feat: support glamsterdam (gloas) networks
  • b6e5b978f1c457617993278f7db4d0ddd53b33c1 fix(agent): bound all fetches under one shared budget
  • 566c09bb69b98a0dabc9939186985469afcc56b8 fix(agent): bound concurrent beacon state and bad block fetches (#64)
  • 2ca68886115dad82155a70b7873aab028c566d43 fix(agent): bound concurrent execution payload envelope fetches
  • 74db3c457e03f743d73ebf135ae934e1723058a0 fix(agent): stream debug_getBadBlocks instead of buffering the node's whole history
  • 41d560738137c4ad66960759171215e167f918e8 fix(ci): pin goreleaser to the triggering tag
  • 7659a51a25a489bc1e0fd9b7e1f28afd806ef4a4 fix(store): delete one object at a time when the S3 endpoint carries a path
  • fa56a345c97a1bdbe6493b8c42457edb5805fdde refactor(agent): drop ethkit in favour of upstream go-ethereum
Commits
  • bf18f8d Merge pull request #68 from ethpandaops/feat/gloas-to-master
  • 7659a51 fix(store): delete one object at a time when the S3 endpoint carries a path
  • c665780 chore(deps): pin beacon to the v0.71.0 gloas release
  • df1dc19 chore(deps): patch reachable govulncheck findings
  • cdc43d4 test: pull minio from pgsty now that Docker Hub no longer serves minio/minio
  • daba603 chore(deps): move gloas support onto released dependencies
  • fa56a34 refactor(agent): drop ethkit in favour of upstream go-ethereum
  • 74db3c4 fix(agent): stream debug_getBadBlocks instead of buffering the node's whole h...
  • 9f44ea1 Archive and promote the envelope half of a gloas slot
  • 3efddf7 Promotion service on devnet-8: merge #65, and fix what the capture pipeline m...
  • Additional commits viewable in compare view

Updates github.com/grpc-ecosystem/grpc-gateway/v2 from 2.30.0 to 2.31.0

Release notes

Sourced from github.com/grpc-ecosystem/grpc-gateway/v2's releases.

v2.31.0

What's Changed

New Contributors

Full Changelog: grpc-ecosystem/grpc-gateway@v2.30.0...v2.31.0

Commits
  • 1dbf071 runtime: deep wildcard (**) must not match zero segments after a preceding li...
  • 53e28c4 chore(deps): update google/oss-fuzz digest to bd2ce21 (#7413)
  • 84afe50 chore(deps): update googleapis digest to 665784f (#7411)
  • dc62ab3 chore(deps): update google/oss-fuzz digest to bee2a55 (#7410)
  • 87fcd67 protoc-gen-openapiv2: allow proto files without a go_package option (#7409)
  • e534705 fix(deps): update module github.com/go-openapi/errors to v0.22.9 (#7408)
  • 5fc39f4 chore(deps): update googleapis digest to cdf35e7 (#7407)
  • a2e3b17 chore(deps): update dependency com_github_bazelbuild_buildtools to v10.1.0 (#...
  • 296885a chore(deps): update googleapis digest to d22e357 (#7406)
  • ca06c22 parse integer and enum path params as base 10 in convert.go (#7405)
  • Additional commits viewable in compare view

Updates github.com/moby/moby/api from 1.56.0 to 1.56.1

Release notes

Sourced from github.com/moby/moby/api's releases.

api/v1.56.1

1.56.1

Changelog

Commits
  • 14ebc60 Merge pull request #53830 from tonistiigi/update-buildkit-v0.34.0-rc1
  • 8eded0e Merge pull request #53671 from thaJeztah/add_WithHTTPRequestHook
  • c4e39af Merge pull request #53596 from vvoland/c8d-refactor-imgload
  • b8a569e client: add WithHTTPRequestHook option
  • 0fed273 Merge pull request #53803 from thaJeztah/etchosts_cleanups
  • 80c72a3 Merge pull request #53831 from corhere/fix-dnsproxy-servfail-test
  • 1cfa161 daemon/containerd: Split image loading into import and unpack steps
  • e7272aa Merge pull request #53606 from flostellbrink/fix/swagger-yaml-indentation
  • 357096e libnetwork/etchosts: keep file open when updating hosts
  • 012b2ef libnetwork/etchosts: propagate file close errors
  • Additional commits viewable in compare view

Updates github.com/moby/moby/client from 0.6.0 to 0.6.1

Release notes

Sourced from github.com/moby/moby/client's releases.

client/v0.6.1

0.6.1

Changelog

Changelog

Sourced from github.com/moby/moby/client's changelog.

0.6.1 (2013-08-23)

  • Registry: Pass "meta" headers in API calls to the registry
  • Packaging: Use correct upstart script with new build tool
  • Packaging: Use libffi-dev, don't build it from sources
  • Packaging: Removed duplicate mercurial install command
Commits
  • 5105263 Bump to v0.6.1
  • 7b5c579 Use correct upstart script with new build tool
  • 15d658d Removed duplicate mercurial install command
  • 59281d6 use libffi-dev, don't build it from sources
  • 29be20f Fixed: ImagePull in runtime test
  • 5a8c32d Use additional decorator in RequestFactory to pass meta headers to registry
  • 588f8e1 Merge pull request #1628 from dotcloud/bump_0.6.0
  • See full diff in compare view

Updates github.com/redis/go-redis/v9 from 9.22.0 to 9.23.0

Release notes

Sourced from github.com/redis/go-redis/v9's releases.

9.23.0

This is a minor release. It contains everything from 9.23.0-beta.1, so these notes cover the full 9.22.0 → 9.23.0 upgrade.

⚠️ Changes to check when you upgrade from 9.22.0:

  • Go 1.26 is now the minimum Go version (#4060). The go directive of the root module and of the submodules moved from 1.24 to 1.26, as part of the dependency bumps for govulncheck findings. Projects that build with Go 1.24 or 1.25 must upgrade the toolchain.
  • Each Client has a dedicated pipeline connection pool (#4002). This includes failover clients and cluster node clients. Pipeline, TxPipeline, and autopipeline operations use this pool, so they do not compete with regular commands for main-pool connections. The pool is for burst capacity only: it dials only when necessary, an unused pool holds zero connections, and if the pool is full an operation uses the main pool. Set PipelinePoolSize: -1 to get the previous single-pool behavior.
  • AutoPipelineOptions.MaxBatchBytes has a default of 128 KiB (before, there was no limit). The default prevents a write/reply deadlock; it is not a throughput control. The buffers of the pipeline pool also have a default of 128 KiB.

⚠️ Changes to experimental APIs since 9.23.0-beta.1 (no effect if you upgrade from 9.22.0):

  • AutoPipelineOptions.FullDuplexFastSubmit is removed (#4018). The submit channel is replaced by a queue that takes a full wave of commands in one lock, so the separate fast path is not necessary. Remove the field from your options.
  • Options.ClientSideCacheRefreshRecencyWindow is removed (#4034). Refresh-on-invalidate now reads again every cached entry of an invalidated key and does not look at how recently the entry was read. On a write-heavy keyspace this means refresh traffic across the full resident cache. Remove the field from your options.
  • LocalCache.LRUClock() is removed (#4034). It returned the recency token that the removed recency window used, and has no replacement. Remove calls to it.
  • ClientSideCacheInvalidationBatchWindow served stale values in beta.1 (#4033). Under load the batcher applied only ~15% of invalidations, and the cache served invalidated values with a ~100% hit rate. 9.23.0 applies all of them. If you used this option on beta.1, upgrade.

🚀 Highlights

Full-Duplex Auto-Pipelining (Experimental)

Set AutoPipelineOptions.FullDuplex to enable the full-duplex mode of the automatic pipeliner. The default mode sends one batch per round trip. In full-duplex mode the engine holds one pipeline-pool connection, and a writer goroutine and a reader goroutine move the ordered command stream in both directions at the same time. On a high-latency link each command completes in approximately one round-trip time (RTT) on a single connection. On a 50 ms WAN profile: ~389k ops/s at 52 ms p50, against ~207k ops/s at 116 ms on the half-duplex ordered path.

The mode works on both faces of a standalone Client (AutoPipeline() and AsyncAutoPipeline()), and natively on a ClusterClient when routing goes to masters only. On a cluster, one child engine per master sends each command to the node that owns its slot, and follows MOVED / ASK redirects and retryable replies (LOADING, READONLY, ...) through the usual cluster redirect path. With replica routing (ReadOnly, RouteByLatency, or RouteRandomly), the autopipeliner uses the half-duplex shard flushers, which obey the shard picker. Config().FullDuplex reports the mode in effect.

Options:

  • FullDuplexWindow — the maximum number of commands in flight (backpressure).
  • FullDuplexIdleTimeout and FullDuplexMaxHold — when the engine returns the held connection to the pool. The pool hooks then do re-authentication and maintenance-notification handoffs.
  • MaxFlushDelay — now also used in full-duplex mode (#4014). The writer waits only when enough commands are in flight, so low-concurrency callers keep the 1×RTT behavior. With MaxFlushDelay=250µs at 1024 callers: +22% ops/s and −26% p99. The default is 0, so this is opt-in.
  • NumShards — on a standalone Client, the number of full-duplex engines (#4022). See below.

Pipeline() on the full-duplex connection (#4021). Standalone Client only. Before, ap.Pipeline() used a pooled connection for each Exec. It now submits the batch to the engine as one contiguous run (FDPipelined), so replies come back in submit order, as on a dedicated connection. At 256–1024 callers with 10 commands per Exec: +49% to +52% throughput on one socket instead of ~150. Errors, retries, hooks, and metrics behave like an ordinary pipeline. A batch that cannot use the stream (a blocking command, a per-command read timeout, a diverted command, or a batch larger than the queue) falls back to the ordinary pipeline. TxPipeline stays on a pooled connection, because MULTI/EXEC needs connection affinity. On a ClusterClient, ap.Pipeline() is still the ordinary cluster pipeline. A batch that the queue cannot admit now reserves its slots and waits in a first-come line, so single commands cannot starve a long pipeline (#4057, merged as part of #4021) by @​vlady-kotsev.

Several engines on one client (#4022). With FullDuplex, NumShards > 1 now means N engines on one client: one pool, one hook chain, N held connections. Commands route by a hash of their first key, so commands on the same key stay on one connection and keep their order without Unordered. Keyless commands are distributed round-robin. An FDPipelined batch stays on one engine. The pipeline pool must hold at least NumShards connections for each full-duplex autopipeliner. More engines help only under high concurrency: with 10-command pipelines, 8 engines were 30% slower than 1 at 8 callers, equal at about 128 callers, and 2.2× faster at 1024 callers.

The full-duplex path supports blocking commands, Options.Limiter (one admission per written batch), per-command and pipeline hooks, OTel metrics, retry budgets (a NoRetry command is never sent again after it is on the wire), and seamless maintenance handoffs. Limits of the stream model:

  • A hook can observe a command, but cannot stop it. A ProcessHook that returns without calling next does not cancel the command on the full-duplex path; the command is already queued on the held connection. Run policy or kill-switch hooks on a plain client or on the half-duplex autopipeliner.
  • Diverted commands are not ordered with the stream. The engine diverts blocking commands, connection-hostile commands, and managed HIMPORT commands. On the async face, wait for the result of a diverted command before you submit a command that depends on it.
  • Single commands on the full-duplex stream do not use the client-side cache. If CSC is enabled, a cacheable command on the stream does not read or write the cache.
  • Duration metrics are recorded per reply. A command that fails before it reaches the reader (lease failure, limiter denial, retry exhaustion, close) calls the error callback but records no operation-duration sample.
rdb := redis.NewClient(&redis.Options{
	Addr: "localhost:6379",
	AutoPipelineOptions: &redis.AutoPipelineOptions{
		FullDuplex: true, // stream commands on one held connection, ~1 RTT each
	},
})
defer rdb.Close()
</tr></table>

... (truncated)

Changelog

Sourced from github.com/redis/go-redis/v9's changelog.

9.23.0 (2026-10-05)

This is a minor release. It contains everything from 9.23.0-beta.1, so these notes cover the full 9.22.0 → 9.23.0 upgrade. The release adds:

  • An experimental full-duplex mode for the automatic pipeliner, now with Pipeline() on the full-duplex connection and several engines on one client.
  • Refresh-on-invalidate and miss coalescing for client-side caching, and a faster cache read path.
  • Better distribution of cluster reads under latency-based routing.
  • Client.EphemeralConn, an opt-in limit on queued autopipeline commands, and many stability fixes.

⚠️ Changes to check when you upgrade from 9.22.0:

  • Go 1.26 is now the minimum Go version (#4060). The go directive of the root module and of the submodules moved from 1.24 to 1.26, as part of the dependency bumps for govulncheck findings. Projects that build with Go 1.24 or 1.25 must upgrade the toolchain.
  • Each Client has a dedicated pipeline connection pool (#4002). This includes failover clients and cluster node clients. Pipeline, TxPipeline, and autopipeline operations use this pool, so they do not compete with regular commands for main-pool connections. The pool is for burst capacity only: it dials only when necessary, an unused pool holds zero connections, and if the pool is full an operation uses the main pool. Set PipelinePoolSize: -1 to get the previous single-pool behavior.
  • AutoPipelineOptions.MaxBatchBytes has a default of 128 KiB (before, there was no limit). The default prevents a write/reply deadlock; it is not a throughput control. The buffers of the pipeline pool also have a default of 128 KiB.

⚠️ Changes to experimental APIs since 9.23.0-beta.1 (no effect if you upgrade from 9.22.0):

  • AutoPipelineOptions.FullDuplexFastSubmit is removed (#4018). The submit channel is replaced by a queue that takes a full wave of commands in one lock, so the separate fast path is not necessary. Remove the field from your options.
  • Options.ClientSideCacheRefreshRecencyWindow is removed (#4034). Refresh-on-invalidate now reads again every cached entry of an invalidated key and does not look at how recently the entry was read. On a write-heavy keyspace this means refresh traffic across the full resident cache. Remove the field from your options.
  • LocalCache.LRUClock() is removed (#4034). It returned the recency token that the removed recency window used, and has no replacement. Remove calls to it.
  • ClientSideCacheInvalidationBatchWindow served stale values in beta.1 (#4033). Under load the batcher applied only ~15% of invalidations, and the cache served invalidated values with a ~100% hit rate. 9.23.0 applies all of them. If you used this option on beta.1, upgrade.

🚀 Highlights

Full-Duplex Auto-Pipelining (Experimental)

Set AutoPipelineOptions.FullDuplex to enable the full-duplex mode of the automatic pipeliner. The default mode sends one batch per round trip. In full-duplex mode the engine holds one pipeline-pool connection, and a writer goroutine and a reader goroutine move the ordered command stream in both directions at the same time. On a high-latency link each command completes in approximately one round-trip time (RTT) on a single connection. On a 50 ms WAN profile: ~389k ops/s at 52 ms p50, against ~207k ops/s at 116 ms on the half-duplex ordered path.

The mode works on both faces of a standalone Client (AutoPipeline() and AsyncAutoPipeline()), and natively on a ClusterClient when routing goes to masters only. On a cluster, one child engine per master sends each command to the node that owns its slot, and follows MOVED / ASK redirects and retryable replies (LOADING, READONLY, ...) through the usual cluster redirect path. With replica routing (ReadOnly, RouteByLatency, or RouteRandomly), the autopipeliner uses the half-duplex shard flushers, which obey the shard picker. Config().FullDuplex reports the mode in effect.

Options:

  • FullDuplexWindow — the maximum number of commands in flight (backpressure).
  • FullDuplexIdleTimeout and FullDuplexMaxHold — when the engine returns the held connection to the pool. The pool hooks then do re-authentication and maintenance-notification handoffs.
  • MaxFlushDelay — now also used in full-duplex mode (#4014). The writer waits only when enough commands are in flight, so low-concurrency callers keep the 1×RTT behavior. With MaxFlushDelay=250µs at 1024 callers: +22% ops/s and −26% p99. The default is 0, so this is opt-in.
  • NumShards — on a standalone Client, the number of full-duplex engines (#4022). See below.

Pipeline() on the full-duplex connection (#4021). Standalone Client only. Before, ap.Pipeline() used a pooled connection for each Exec. It now submits the batch to the engine as one contiguous run (FDPipelined), so replies come back in submit order, as on a dedicated connection. At 256–1024 callers with 10 commands per Exec: +49% to +52% throughput on one socket instead of ~150. Errors, retries, hooks, and metrics behave like an ordinary pipeline. A batch that cannot use the stream (a blocking command, a per-command read timeout, a diverted command, or a batch larger than the queue) falls back to the ordinary pipeline. TxPipeline stays on a pooled connection, because MULTI/EXEC needs connection affinity. On a ClusterClient, ap.Pipeline() is still the ordinary cluster pipeline. A batch that the queue cannot admit now reserves its slots and waits in a first-come line, so single commands cannot starve a long pipeline (#4057, merged as part of #4021) by @​vlady-kotsev.

Several engines on one client (#4022). With FullDuplex, NumShards > 1 now means N engines on one client: one pool, one hook chain, N held connections. Commands route by a hash of their first key, so commands on the same key stay on one connection and keep their order without Unordered. Keyless commands are distributed round-robin. An FDPipelined batch stays on one engine. The pipeline pool must hold at least NumShards connections for each full-duplex autopipeliner. More engines help only under high concurrency: with 10-command pipelines, 8 engines were 30% slower than 1 at 8 callers, equal at about 128 callers, and 2.2× faster at 1024 callers.

The full-duplex path supports blocking commands, Options.Limiter (one admission per written batch), per-command and pipeline hooks, OTel metrics, retry budgets (a NoRetry command is never sent again after it is on the wire), and seamless maintenance handoffs. Limits of the stream model:

  • A hook can observe a command, but cannot stop it. A ProcessHook that returns without calling next does not cancel the command on the full-duplex path; the command is already queued on the held connection. Run policy or kill-switch hooks on a plain client or on the half-duplex autopipeliner.
  • Diverted commands are not ordered with the stream. The engine diverts blocking commands, connection-hostile commands, and managed HIMPORT commands. On the async face, wait for the result of a diverted command before you submit a command that depends on it.
  • Single commands on the full-duplex stream do not use the client-side cache. If CSC is enabled, a cacheable command on the stream does not read or write the cache.
  • Duration metrics are recorded per reply. A command that fails before it reaches the reader (lease failure, limiter denial, retry exhaustion, close) calls the error callback but records no operation-duration sample.
rdb := redis.NewClient(&redis.Options{
</tr></table>

... (truncated)

Commits
  • 6f2b263 chore(release): v9.23.0 (#4074)
  • ec50c69 feat(conn): add DisposableConn to discard on Close (#4039)
  • e3d2548 fix(pool): fix ConnStateMachine waiter races (#4072)
  • 2ee6d86 fix(pool): wake waiters when a connection is released to the pool (#4028)
  • 83d45ed fix:(proto): support uintptr in WriteArg (#4054)
  • c2002af docs(example): add full-duplex examples (#4061)
  • b5f8864 feat(autopipeline): add MaxQueuedCommands hard limit (#4070)
  • 89ecbc5 fix(options): reject invalid skip_verify values in ParseURL (#4064)
  • f813adc feat(autopipeline): run N full-duplex engines on one client (#4022)
  • 349bcf4 feat(autopipeline): run Pipeline on the full-duplex connection (#4021)
  • Additional commits viewable in compare view

Updates golang.org/x/sys from 0.48.0 to 0.49.0

Commits
  • b6b8557 unix/linux: unify ppc64x syscall wrappers
  • aab6988 unix: add PrctlArg5Ptr
  • cdfd984 unix: pass fcntl data as unsafe.Pointer in FcntlF{lock,store} on darwin
  • 782b836 unix/linux: don't warn about closed stderr from child process
  • 61592fb unix: return syscall error in *listxattrNS on BSD
  • c136fda unix/linux/Dockerfile: update to Go 1.26.8
  • f1d0d79 unix: pass xattr data as unsafe.Pointer in BSD xattr syscalls
  • 67f850b unix: update linux to v7.2
  • eb1f659 unix: add O_EXEC and O_SEARCH on darwin
  • 51bc731 unix: add Mmsghdr for linux
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
build(deps): bump the go-minor-patch group across 1 directory with 7 …
a127af8 
…updates

Bumps the go-minor-patch group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [github.com/ethpandaops/cbt](https://github.com/ethpandaops/cbt) | `0.1.6` | `0.1.9` |
| [github.com/ethpandaops/tracoor](https://github.com/ethpandaops/tracoor) | `0.0.33` | `0.1.0` |
| [github.com/grpc-ecosystem/grpc-gateway/v2](https://github.com/grpc-ecosystem/grpc-gateway) | `2.30.0` | `2.31.0` |
| [github.com/moby/moby/api](https://github.com/moby/moby) | `1.56.0` | `1.56.1` |
| [github.com/moby/moby/client](https://github.com/moby/moby) | `0.6.0` | `0.6.1` |
| [github.com/redis/go-redis/v9](https://github.com/redis/go-redis) | `9.22.0` | `9.23.0` |
| [golang.org/x/sys](https://github.com/golang/sys) | `0.48.0` | `0.49.0` |



Updates `github.com/ethpandaops/cbt` from 0.1.6 to 0.1.9
- [Release notes](https://github.com/ethpandaops/cbt/releases)
- [Commits](ethpandaops/cbt@v0.1.6...v0.1.9)

Updates `github.com/ethpandaops/tracoor` from 0.0.33 to 0.1.0
- [Release notes](https://github.com/ethpandaops/tracoor/releases)
- [Commits](ethpandaops/tracoor@v0.0.33...v0.1.0)

Updates `github.com/grpc-ecosystem/grpc-gateway/v2` from 2.30.0 to 2.31.0
- [Release notes](https://github.com/grpc-ecosystem/grpc-gateway/releases)
- [Commits](grpc-ecosystem/grpc-gateway@v2.30.0...v2.31.0)

Updates `github.com/moby/moby/api` from 1.56.0 to 1.56.1
- [Release notes](https://github.com/moby/moby/releases)
- [Commits](moby/moby@api/v1.56.0...api/v1.56.1)

Updates `github.com/moby/moby/client` from 0.6.0 to 0.6.1
- [Release notes](https://github.com/moby/moby/releases)
- [Changelog](https://github.com/moby/moby/blob/v0.6.1/CHANGELOG.md)
- [Commits](moby/moby@v0.6.0...v0.6.1)

Updates `github.com/redis/go-redis/v9` from 9.22.0 to 9.23.0
- [Release notes](https://github.com/redis/go-redis/releases)
- [Changelog](https://github.com/redis/go-redis/blob/master/RELEASE-NOTES.md)
- [Commits](redis/go-redis@v9.22.0...v9.23.0)

Updates `golang.org/x/sys` from 0.48.0 to 0.49.0
- [Commits](golang/sys@v0.48.0...v0.49.0)

---
updated-dependencies:
- dependency-name: github.com/ethpandaops/cbt
  dependency-version: 0.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-minor-patch
- dependency-name: github.com/ethpandaops/tracoor
  dependency-version: 0.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-patch
- dependency-name: github.com/grpc-ecosystem/grpc-gateway/v2
  dependency-version: 2.31.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-patch
- dependency-name: github.com/moby/moby/api
  dependency-version: 1.56.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-minor-patch
- dependency-name: github.com/moby/moby/client
  dependency-version: 0.6.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-minor-patch
- dependency-name: github.com/redis/go-redis/v9
  dependency-version: 9.23.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-patch
- dependency-name: golang.org/x/sys
  dependency-version: 0.49.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Oct 21, 2026
@redpandabot

redpandabot Bot commented Oct 21, 2026

Copy link
Copy Markdown

CI failed @ a127af80

staticcheck SA1019 fired twice: cbtapi.GetSwagger() is deprecated in cbt v0.1.9 (verified via GitHub API: pkg/api/generated/server.gen.go:2135 has the Deprecated comment; GetSpec at :2096 has identical signature). The PR only changes go.mod/go.sum, bumping github.com/ethpandaops/cbt v0.1.6 -> v0.1.9; the test file is unchanged (same GetSwagger calls at lines 42 and 75 on origin/master). The dependency bump introduces the deprecation marker, so the lint failure is caused by this PR.

  • CI / lint — caused by this PR — Dependabot bump of github.com/ethpandaops/cbt v0.1.6 -> v0.1.9 in go.mod introduced a // Deprecated: marker on generated.GetSwagger; staticcheck (golangci-lint v2.15.0) then flags the two existing GetSwagger() calls in the unchanged test file as SA1019. (pkg/server/operations_cbt_contract_test.go:42) — Replace cbtapi.GetSwagger() with cbtapi.GetSpec() at pkg/server/operations_cbt_contract_test.go:42 and :75 (drop-in replacement, same signature/return type).
  • CI / lint second identical finding — caused by this PR — Same SA1019 deprecation error at the second GetSwagger() call site in the same unchanged test file, triggered by the same cbt v0.1.9 bump. (pkg/server/operations_cbt_contract_test.go:75) — Replace cbtapi.GetSwagger() with cbtapi.GetSpec() at pkg/server/operations_cbt_contract_test.go:75.

Diagnosed CI @ a127af80
"Simplicity is prerequisite for reliability." — Edsger Dijkstra

@dependabot @github

dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 26, 2026
@dependabot
dependabot Bot deleted the dependabot/go_modules/go-minor-patch-5d029c1834 branch October 26, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants