Skip to content

deps(cli): bump the go-deps group across 1 directory with 12 updates - #238

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/apps/cli/go-deps-76d49cb1a2
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/apps/cli/go-deps-76d49cb1a2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 25, 2026 •

Copy link
Copy Markdown

Bumps the go-deps group with 12 updates in the /apps/cli directory:

Package From To
github.com/aws/aws-sdk-go-v2/feature/rds/auth 1.7.4 1.7.6
github.com/aws/aws-sdk-go-v2/service/dynamodb 1.56.1 1.72.0
github.com/aws/aws-sdk-go-v2/service/lambda 1.110.0 1.113.2
github.com/aws/aws-sdk-go-v2/service/s3 1.114.3 1.114.4
github.com/aws/aws-sdk-go-v2/service/secretsmanager 1.50.1 1.50.5
github.com/aws/aws-sdk-go-v2/service/ssm 1.79.0 1.80.0
github.com/docker/go-connections 0.6.0 0.8.2
github.com/fsnotify/fsnotify 1.9.0 1.10.1
github.com/minio/minio-go/v7 7.0.99 7.4.1
github.com/newstack-cloud/bluelink/libs/blueprint-state 0.9.1 0.10.0
github.com/newstack-cloud/bluelink/libs/common 0.4.0 0.5.0
github.com/redis/go-redis/v9 9.18.0 9.23.0

Updates github.com/aws/aws-sdk-go-v2/feature/rds/auth from 1.7.4 to 1.7.6

Commits

Updates github.com/aws/aws-sdk-go-v2/service/dynamodb from 1.56.1 to 1.72.0

Commits

Updates github.com/aws/aws-sdk-go-v2/service/lambda from 1.110.0 to 1.113.2

Commits

Updates github.com/aws/aws-sdk-go-v2/service/s3 from 1.114.3 to 1.114.4

Commits

Updates github.com/aws/aws-sdk-go-v2/service/secretsmanager from 1.50.1 to 1.50.5

Commits
  • a4cce72 Release 2026-10-19
  • b9fa987 Regenerated Clients
  • 6053b94 Update API model
  • 04c5879 EventBridge endpoint test only assert scheme + host (#3592)
  • acc7f17 Fix allow null values into non-sparse lists as zero-value (#3590)
  • 4486a31 s3/transfermanager: fix panic in concurrentReader when len(p) is smaller than...
  • fdedcfa Release 2026-10-14
  • b23ae98 Regenerated Clients
  • 3f0de9a Update endpoints model
  • 14be3b3 Update API model
  • Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/service/ssm from 1.79.0 to 1.80.0

Commits

Updates github.com/docker/go-connections from 0.6.0 to 0.8.2

Release notes

Sourced from github.com/docker/go-connections's releases.

v0.8.2

What's Changed

  • sockets: preserve configured TLS ALPN protocols
  • ci: add dependabot to update actions
  • ci: update runners to Ubuntu 26.04
  • build(deps): bump actions/checkout from 6.0.2 to 7.0.1
  • build(deps): bump actions/setup-go from 6.3.0 to 7.0.0
  • build(deps): bump golangci/golangci-lint-action from 9.2.0 to 9.3.0

Full Changelog: docker/go-connections@v0.8.1...v0.8.2

Commits
  • 5032217 Merge pull request #171 from thaJeztah/bump_ubuntu
  • 91e2669 Merge pull request #172 from docker/dependabot/github_actions/golangci/golang...
  • 4825d28 Merge pull request #174 from docker/dependabot/github_actions/actions/setup-g...
  • 36e3075 Merge pull request #173 from docker/dependabot/github_actions/actions/checkou...
  • 745bbf6 build(deps): bump actions/setup-go from 6.3.0 to 7.0.0
  • 76a625d build(deps): bump actions/checkout from 6.0.2 to 7.0.1
  • 3be4490 build(deps): bump golangci/golangci-lint-action from 9.2.0 to 9.3.0
  • 61b16f0 Merge pull request #170 from thaJeztah/add_dependabot
  • afe2450 ci: update runners to Ubuntu 26.04
  • 29cd53e ci: add dependabot to update actions
  • Additional commits viewable in compare view

Updates github.com/fsnotify/fsnotify from 1.9.0 to 1.10.1

Release notes

Sourced from github.com/fsnotify/fsnotify's releases.

v1.10.1

Changes and fixes

  • inotify: don't remove sibling watches sharing a path prefix (#754)

  • inotify, windows: don't rename sibling watches sharing a path prefix (#755)

#754: fsnotify/fsnotify#754 #755: fsnotify/fsnotify#755

v1.10.0

This version of fsnotify needs Go 1.23.

Changes and fixes

  • inotify: improve initialization error message (#731)

  • inotify: send Rename event if recursive watch is renamed (#696)

  • inotify: avoid copying event buffers when reading names (#741)

  • kqueue: skip dangling symlinks (ENOENT) in watchDirectoryFiles, so a bad entry no longer aborts Watcher.Add for the whole directory (#748)

  • kqueue: drop watches directly in Close() to fix a file descriptor leak when recycling watchers (#740)

  • windows: fix nil pointer dereference in remWatch (#736)

  • windows: lock watch field updates against concurrent WatchList to fix a race introduced in v1.9.0 (#709, #749)

#696: fsnotify/fsnotify#696 #709: fsnotify/fsnotify#709 #731: fsnotify/fsnotify#731 #736: fsnotify/fsnotify#736 #740: fsnotify/fsnotify#740 #741: fsnotify/fsnotify#741 #748: fsnotify/fsnotify#748 #749: fsnotify/fsnotify#749

Changelog

Sourced from github.com/fsnotify/fsnotify's changelog.

1.10.1 2026-05-04

Changes and fixes

  • inotify: don't remove sibling watches sharing a path prefix (#754)

  • inotify, windows: don't rename sibling watches sharing a path prefix (#755)

#754: fsnotify/fsnotify#754 #755: fsnotify/fsnotify#755

1.10.0 2026-04-30

This version of fsnotify needs Go 1.23.

Changes and fixes

  • inotify: improve initialization error message (#731)

  • inotify: send Rename event if recursive watch is renamed (#696)

  • inotify: avoid copying event buffers when reading names (#741)

  • kqueue: skip dangling symlinks (ENOENT) in watchDirectoryFiles, so a bad entry no longer aborts Watcher.Add for the whole directory (#748)

  • kqueue: drop watches directly in Close() to fix a file descriptor leak when recycling watchers (#740)

  • windows: fix nil pointer dereference in remWatch (#736)

  • windows: lock watch field updates against concurrent WatchList to fix a race introduced in v1.9.0 (#709, #749)

#696: fsnotify/fsnotify#696 #709: fsnotify/fsnotify#709 #731: fsnotify/fsnotify#731 #736: fsnotify/fsnotify#736 #740: fsnotify/fsnotify#740 #741: fsnotify/fsnotify#741 #748: fsnotify/fsnotify#748 #749: fsnotify/fsnotify#749

Commits
  • 76b01a6 Release 1.10.1
  • fec150b Update changelog
  • 162b421 inotify, windows: don't rename sibling watches sharing a path prefix (#755)
  • 224257f inotify: don't remove sibling watches sharing a path prefix (#754)
  • e0c956c windows: document directory Write events and stabilize tests (#745)
  • 8d01d7b Release 1.10.0
  • 602284e Update changelog
  • 7f03e59 kqueue: skip ENOENT entries in watchDirectoryFiles (#748)
  • dab9dde windows: lock watch field updates against concurrent WatchList (#709) (#749)
  • eadf267 kqueue: drop watches directly in Close() instead of going through remove() (#...
  • Additional commits viewable in compare view

Updates github.com/minio/minio-go/v7 from 7.0.99 to 7.4.1

Release notes

Sourced from github.com/minio/minio-go/v7's releases.

v7.4.1

What's Changed

Full Changelog: minio/minio-go@v7.4.0...v7.4.1

v7.4.0

Go 1.26 or later is now required. Go 1.25 is out of support, and golang.org/x/net v0.60.0 (the fix for GO-2026-6603, 6610, 6611, 6612 and 6617) requires Go 1.26 (#2313).

What's Changed

New Contributors

... (truncated)

Commits
  • 1a663bb update lib version to v7.4.1
  • c68b12c fix: abort failed uploads even when the caller cancels (#2318)
  • 8a72fb4 update lib version to v7.4.0
  • 85df9ce get: add opt-in parallel range GET via ParallelWorkers (#2317)
  • 91dc4dd fix: send RetainUntilDate in UTC (#2315)
  • 79b8caa compose: allow parallel upload-part-copy with NumThreads (#2316)
  • 1ab9013 docs: fix 'Recieved' typo in CancelBucketReplicationResync (#2314)
  • 21d2ec1 fix: trim whitespace from bucket location (#2274)
  • 450a9b3 credentials: allow NewKubernetesIdentity to read a projected token file (#2312)
  • aeb0641 docs: remove broken Slack badges (#2304)
  • Additional commits viewable in compare view

Updates github.com/newstack-cloud/bluelink/libs/blueprint-state from 0.9.1 to 0.10.0

Release notes

Sourced from github.com/newstack-cloud/bluelink/libs/blueprint-state's releases.

plugin-framework: v0.10.0

0.10.0 (2026-05-10)

Features

  • plugin-framework: thread go context through transform pipeline (ad67837)

blueprint-state: v0.10.0

0.10.0 (2026-10-14)

Features

  • blueprint-state: add key provider implementations for the main providers (a3775cc)
  • blueprint-state: add re-encryption helpers and make state container support encryption (1bedc70)
  • blueprint-state: add support for encryption in statestore storage (367bec6)
Commits
  • 82df4cd chore(blueprint): add change log entry for 0.10.0
  • 1f1b973 feat(blueprint): add allowed values to resource definitions schema
  • 958af07 feat(deploy-engine-client): add query params for creating blueprint validations
  • 36a98e1 feat(deploy-engine): integrate plugin config validation into change staging a...
  • 2955935 feat(deploy-engine): add functionality to validate plugin configuration
  • bd38518 chore(blueprint): add change log entry for v0.9.0
  • 8393487 docs: correct celerity framework domain
  • 9f2b9a2 feat(blueprint): add functionality to populate defaults and validate plugin c...
  • 0eaffb3 feat(blueprint): add new allow additional fields property to config definition
  • 9163198 feat(plugin-docgen): add support for new allow additional fields property in ...
  • Additional commits viewable in compare view

Updates github.com/newstack-cloud/bluelink/libs/common from 0.4.0 to 0.5.0

Release notes

Sourced from github.com/newstack-cloud/bluelink/libs/common's releases.

blueprint-state: v0.5.0

0.5.0 (2026-01-06)

Features

  • blueprint-state: add computed fields to resource state (0811266)
  • blueprint-state: add functionality to list blueprint instances (377139a)
  • blueprint-state: add persistence for link drift (a778aa6)
  • blueprint-state: add persistence for reconciliation results (9f16d59)
  • blueprint-state: add support for getting the last event id for a given channel (f4dace1)
  • blueprint-state: add support for saving system metadata for resources (7b4a455)

Bug Fixes

  • blueprint-state: add fix for memfile drift persistence when drift files are not present (8c1519e)
  • blueprint-state: add fix to make sure starting event id is exclusive in memfile (6966017)

Dependencies

  • blueprint-state: update blueprint core lib (3f33990)

plugin-framework: v0.5.0

0.5.0 (2026-04-19)

Features

  • plugin-framework: add support for transformer abstract links and concrete link validation (eef22e9)

Dependencies

  • plugin-framework: bump the go-deps group across 1 directory with 2 updates (39abecc)

deploy-engine: v0.5.0

0.5.0 (2026-04-20)

Features

  • deploy-engine: add support for removal policies (d60c431)

deploy-engine-client: v0.5.0

0.5.0 (2026-05-09)

Features

... (truncated)

Commits
  • 7aac32e chore: release cli 0.5.0
  • 8b02bab feat(cli): add support for the blueprint language
  • fbf30e5 chore: release plugin-docgen 0.2.1
  • 808d3fe deps(plugin-docgen): bump up plugin framework and blueprint lib to latest
  • 6d61407 chore: release blueprint-ls 0.4.0
  • 250f109 deps(blueprint-ls): bump up plugin framework to 0.12.0
  • a1c16d4 chore: release plugin-framework 0.12.0
  • 4f772de feat(plugin-framework): add helpers for extracting annotations from bp schema
  • 963dc1c deps(plugin-framework): bump blueprint lib to 0.47.0
  • 9ade512 feat(blueprint-ls): add blueprint language support
  • Additional commits viewable in compare view

Updates github.com/redis/go-redis/v9 from 9.18.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 co...

    Description has been truncated

Bumps the go-deps group with 12 updates in the /apps/cli directory:

| Package | From | To |
| --- | --- | --- |
| [github.com/aws/aws-sdk-go-v2/feature/rds/auth](https://github.com/aws/aws-sdk-go-v2) | `1.7.4` | `1.7.6` |
| [github.com/aws/aws-sdk-go-v2/service/dynamodb](https://github.com/aws/aws-sdk-go-v2) | `1.56.1` | `1.72.0` |
| [github.com/aws/aws-sdk-go-v2/service/lambda](https://github.com/aws/aws-sdk-go-v2) | `1.110.0` | `1.113.2` |
| [github.com/aws/aws-sdk-go-v2/service/s3](https://github.com/aws/aws-sdk-go-v2) | `1.114.3` | `1.114.4` |
| [github.com/aws/aws-sdk-go-v2/service/secretsmanager](https://github.com/aws/aws-sdk-go-v2) | `1.50.1` | `1.50.5` |
| [github.com/aws/aws-sdk-go-v2/service/ssm](https://github.com/aws/aws-sdk-go-v2) | `1.79.0` | `1.80.0` |
| [github.com/docker/go-connections](https://github.com/docker/go-connections) | `0.6.0` | `0.8.2` |
| [github.com/fsnotify/fsnotify](https://github.com/fsnotify/fsnotify) | `1.9.0` | `1.10.1` |
| [github.com/minio/minio-go/v7](https://github.com/minio/minio-go) | `7.0.99` | `7.4.1` |
| [github.com/newstack-cloud/bluelink/libs/blueprint-state](https://github.com/newstack-cloud/bluelink) | `0.9.1` | `0.10.0` |
| [github.com/newstack-cloud/bluelink/libs/common](https://github.com/newstack-cloud/bluelink) | `0.4.0` | `0.5.0` |
| [github.com/redis/go-redis/v9](https://github.com/redis/go-redis) | `9.18.0` | `9.23.0` |



Updates `github.com/aws/aws-sdk-go-v2/feature/rds/auth` from 1.7.4 to 1.7.6
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/m2/v1.7.4...service/m2/v1.7.6)

Updates `github.com/aws/aws-sdk-go-v2/service/dynamodb` from 1.56.1 to 1.72.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.56.1...service/s3/v1.72.0)

Updates `github.com/aws/aws-sdk-go-v2/service/lambda` from 1.110.0 to 1.113.2
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.110.0...service/s3/v1.113.2)

Updates `github.com/aws/aws-sdk-go-v2/service/s3` from 1.114.3 to 1.114.4
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.114.3...service/s3/v1.114.4)

Updates `github.com/aws/aws-sdk-go-v2/service/secretsmanager` from 1.50.1 to 1.50.5
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.50.1...service/acm/v1.50.5)

Updates `github.com/aws/aws-sdk-go-v2/service/ssm` from 1.79.0 to 1.80.0
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.79.0...service/s3/v1.80.0)

Updates `github.com/docker/go-connections` from 0.6.0 to 0.8.2
- [Release notes](https://github.com/docker/go-connections/releases)
- [Commits](docker/go-connections@v0.6.0...v0.8.2)

Updates `github.com/fsnotify/fsnotify` from 1.9.0 to 1.10.1
- [Release notes](https://github.com/fsnotify/fsnotify/releases)
- [Changelog](https://github.com/fsnotify/fsnotify/blob/main/CHANGELOG.md)
- [Commits](fsnotify/fsnotify@v1.9.0...v1.10.1)

Updates `github.com/minio/minio-go/v7` from 7.0.99 to 7.4.1
- [Release notes](https://github.com/minio/minio-go/releases)
- [Commits](minio/minio-go@v7.0.99...v7.4.1)

Updates `github.com/newstack-cloud/bluelink/libs/blueprint-state` from 0.9.1 to 0.10.0
- [Release notes](https://github.com/newstack-cloud/bluelink/releases)
- [Commits](newstack-cloud/bluelink@blueprint-state/v0.9.1...libs/blueprint/v0.10.0)

Updates `github.com/newstack-cloud/bluelink/libs/common` from 0.4.0 to 0.5.0
- [Release notes](https://github.com/newstack-cloud/bluelink/releases)
- [Commits](newstack-cloud/bluelink@cli/v0.4.0...cli/v0.5.0)

Updates `github.com/redis/go-redis/v9` from 9.18.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.18.0...v9.23.0)

---
updated-dependencies:
- dependency-name: github.com/aws/aws-sdk-go-v2/feature/rds/auth
  dependency-version: 1.7.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/aws/aws-sdk-go-v2/service/dynamodb
  dependency-version: 1.72.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/aws/aws-sdk-go-v2/service/lambda
  dependency-version: 1.113.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/aws/aws-sdk-go-v2/service/s3
  dependency-version: 1.114.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/aws/aws-sdk-go-v2/service/secretsmanager
  dependency-version: 1.50.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
- dependency-name: github.com/aws/aws-sdk-go-v2/service/ssm
  dependency-version: 1.80.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/docker/go-connections
  dependency-version: 0.8.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/fsnotify/fsnotify
  dependency-version: 1.10.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/minio/minio-go/v7
  dependency-version: 7.4.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/newstack-cloud/bluelink/libs/blueprint-state
  dependency-version: 0.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: github.com/newstack-cloud/bluelink/libs/common
  dependency-version: 0.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- 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-deps
...

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 25, 2026
@coderabbitai

coderabbitai Bot commented Oct 25, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f30cf9f5-cbda-41ae-9c1b-d48a710c848f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@dependabot @github

dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Author

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

@dependabot dependabot Bot closed this Nov 1, 2026
@dependabot
dependabot Bot deleted the dependabot/go_modules/apps/cli/go-deps-76d49cb1a2 branch November 1, 2026 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants