Skip to content

deps(deps): bump github.com/redis/go-redis/v9 from 9.20.0 to 9.20.1 in the redis group#294

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/main/redis-7884a97628
Closed

deps(deps): bump github.com/redis/go-redis/v9 from 9.20.0 to 9.20.1 in the redis group#294
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/main/redis-7884a97628

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 15, 2026

Copy link
Copy Markdown
Contributor

Bumps the redis group with 1 update: github.com/redis/go-redis/v9.

Updates github.com/redis/go-redis/v9 from 9.20.0 to 9.20.1

Release notes

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

9.20.1

This is a patch release containing bug fixes only. There are no new features or breaking changes; upgrading from 9.20.0 is a drop-in replacement.

🚀 Highlights

RESP3 pub/sub message loss fixed

PeekPushNotificationName previously inspected only the bytes already buffered by bufio, so when a push frame header straddled a buffer fill boundary it could return a truncated notification name (e.g. "messa" instead of "message"). The push processor then mis-routed the frame and ReadReply silently dropped it, causing intermittent RESP3 pub/sub message loss. The peek now grows its window (36 bytes → up to 4 KiB) and reads more from the connection until the header is complete, cleanly separating incomplete prefixes from corrupt frames (including overflow-safe bulk-length handling). Fixes #3839.

(#3842) by @​ndyakov

🐛 Bug Fixes

  • RESP3 push peeking: PeekPushNotificationName no longer returns a truncated notification name when a push frame header spans a buffer boundary, preventing silent RESP3 pub/sub message loss (fixes #3839) (#3842) by @​ndyakov
  • FT.HYBRID vector params: Vector data is now always sent via PARAMS with auto-generated param names (__vector_param_N, with collision avoidance) when VectorParamName is omitted, since Redis no longer accepts inline vector blobs; the FTHybridOptions.Params map is no longer mutated, so the same options struct can be reused across calls (#3844) by @​ndyakov
  • CLUSTER SHARDS forward compatibility: Unknown shard- and node-level attributes in the CLUSTER SHARDS reply are now skipped via DiscardNext() instead of erroring, so clients keep working when the server introduces new fields (#3843) by @​madolson
  • PubSub double reconnect: PubSub.releaseConn no longer reconnects twice when a connection is both unusable (or pending handoff) and reports a bad-connection error, avoiding a wasted connection establish-then-close cycle (#3833) by @​cxljs

👥 Contributors

We'd like to thank all the contributors who worked on this release!

@​cxljs, @​madolson, @​ndyakov


Full Changelog: redis/go-redis@v9.20.0...v9.20.1

Changelog

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

9.20.1 (2026-06-11)

This is a patch release containing bug fixes only. There are no new features or breaking changes; upgrading from 9.20.0 is a drop-in replacement.

🚀 Highlights

RESP3 pub/sub message loss fixed

PeekPushNotificationName previously inspected only the bytes already buffered by bufio, so when a push frame header straddled a buffer fill boundary it could return a truncated notification name (e.g. "messa" instead of "message"). The push processor then mis-routed the frame and ReadReply silently dropped it, causing intermittent RESP3 pub/sub message loss. The peek now grows its window (36 bytes → up to 4 KiB) and reads more from the connection until the header is complete, cleanly separating incomplete prefixes from corrupt frames (including overflow-safe bulk-length handling). Fixes #3839.

(#3842) by @​ndyakov

🐛 Bug Fixes

  • RESP3 push peeking: PeekPushNotificationName no longer returns a truncated notification name when a push frame header spans a buffer boundary, preventing silent RESP3 pub/sub message loss (fixes #3839) (#3842) by @​ndyakov
  • FT.HYBRID vector params: Vector data is now always sent via PARAMS with auto-generated param names (__vector_param_N, with collision avoidance) when VectorParamName is omitted, since Redis no longer accepts inline vector blobs; the FTHybridOptions.Params map is no longer mutated, so the same options struct can be reused across calls (#3844) by @​ndyakov
  • CLUSTER SHARDS forward compatibility: Unknown shard- and node-level attributes in the CLUSTER SHARDS reply are now skipped via DiscardNext() instead of erroring, so clients keep working when the server introduces new fields (#3843) by @​madolson
  • PubSub double reconnect: PubSub.releaseConn no longer reconnects twice when a connection is both unusable (or pending handoff) and reports a bad-connection error, avoiding a wasted connection establish-then-close cycle (#3833) by @​cxljs

👥 Contributors

We'd like to thank all the contributors who worked on this release!

@​cxljs, @​madolson, @​ndyakov


Full Changelog: redis/go-redis@v9.20.0...v9.20.1

Commits
  • a13416b chore(release): 9.20.1 (#3847)
  • 10dc44f fix(push): fix peeking when push name is truncated (#3842)
  • e1a2d68 fix(ft.hybrid): Always generate vector param names if they are not provided b...
  • a4b234f chore(deps): bump codecov/codecov-action from 6 to 7 (#3845)
  • 974e717 fix(command): ignore unknown fields in CLUSTER SHARDS response (#3843)
  • 65d6abd fix(pubsub): prevent double reconnect in releaseConn (#3833)
  • See full diff in compare view

Dependabot compatibility score

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

Bumps the redis group with 1 update: [github.com/redis/go-redis/v9](https://github.com/redis/go-redis).


Updates `github.com/redis/go-redis/v9` from 9.20.0 to 9.20.1
- [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.20.0...v9.20.1)

---
updated-dependencies:
- dependency-name: github.com/redis/go-redis/v9
  dependency-version: 9.20.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: redis
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Dependency updates go Go code or module changes labels Jun 15, 2026
KeiaiLab-PHIL added a commit that referenced this pull request Jul 20, 2026
2026-06 부터 적체된 dependabot go_modules PR 7건(#276 #277 #293 #294 #295
#296 #297)을 개별 머지 대신 `go get -u -t ./... && go mod tidy` 일괄 최신화로
대체한다. 직접 의존성 12건 + 간접 의존성 63건 갱신.

주요 모듈 (before → after):
- k8s.io/api / apimachinery / client-go   v0.36.1  → v0.36.2   (#293)
- k8s.io/utils                            20260210 → 20260707
- google.golang.org/api                   v0.283.0 → v0.289.0  (#297)
- cloud.google.com/go/storage             v1.62.2  → v1.63.1   (#277)
- github.com/Azure/.../sdk/azcore         v1.21.1  → v1.22.0   (#276)
- github.com/Azure/.../storage/azblob     v1.7.0   → v1.8.0
- github.com/redis/go-redis/v9            v9.20.0  → v9.21.0   (#294)
- github.com/onsi/ginkgo/v2               v2.29.0  → v2.32.0   (#295)
- github.com/onsi/gomega                  v1.41.0  → v1.42.1   (#296)
- github.com/minio/minio-go/v7            v7.2.0   → v7.2.1

dependabot 제안 대비 동일하거나 더 최신 버전으로 수렴했다. gomega/ginkgo 는
test-only 의존성이라 `go get -u` 만으로는 갱신되지 않아 `-t` 플래그를 사용했다.

sigs.k8s.io/controller-runtime 은 v0.24.1(최신 stable)을 유지하며, k8s.io/*
는 controller-runtime 호환 범위인 v0.36.x 안에서만 갱신했다 — v0.37.0-alpha.*
는 pre-release 라 `go get -u` 대상에서 제외된다. go 지시자(1.26.0)와
toolchain(go1.26.4) 은 변경하지 않았다.

검증 (go1.26.5 darwin/arm64, 전부 exit 0):
- go build ./...                 → exit 0
- go vet ./...                   → exit 0
- make lint (golangci-lint v2.11.4) → exit 0, "0 issues."
- make test (envtest k8s 1.36.2) → exit 0, 17 패키지 ok / FAIL 0
  internal/controller 53.1% · internal/webhook/v1alpha1 91.1% ·
  internal/resources 92.5% · internal/backuplifecycle·federation·migration 100%

변경 파일은 go.mod / go.sum 뿐이다 (make test 의 manifests·generate·fmt 는
추가 diff 를 만들지 않았다 = 생성물 drift 0).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: phil <phil@keiailab.com>
KeiaiLab-PHIL added a commit that referenced this pull request Jul 20, 2026
2026-06 부터 적체된 dependabot go_modules PR 7건(#276 #277 #293 #294 #295
#296 #297)을 개별 머지 대신 `go get -u -t ./... && go mod tidy` 일괄 최신화로
대체한다. 직접 의존성 12건 + 간접 의존성 63건 갱신.

주요 모듈 (before → after):
- k8s.io/api / apimachinery / client-go   v0.36.1  → v0.36.2   (#293)
- k8s.io/utils                            20260210 → 20260707
- google.golang.org/api                   v0.283.0 → v0.289.0  (#297)
- cloud.google.com/go/storage             v1.62.2  → v1.63.1   (#277)
- github.com/Azure/.../sdk/azcore         v1.21.1  → v1.22.0   (#276)
- github.com/Azure/.../storage/azblob     v1.7.0   → v1.8.0
- github.com/redis/go-redis/v9            v9.20.0  → v9.21.0   (#294)
- github.com/onsi/ginkgo/v2               v2.29.0  → v2.32.0   (#295)
- github.com/onsi/gomega                  v1.41.0  → v1.42.1   (#296)
- github.com/minio/minio-go/v7            v7.2.0   → v7.2.1

dependabot 제안 대비 동일하거나 더 최신 버전으로 수렴했다. gomega/ginkgo 는
test-only 의존성이라 `go get -u` 만으로는 갱신되지 않아 `-t` 플래그를 사용했다.

sigs.k8s.io/controller-runtime 은 v0.24.1(최신 stable)을 유지하며, k8s.io/*
는 controller-runtime 호환 범위인 v0.36.x 안에서만 갱신했다 — v0.37.0-alpha.*
는 pre-release 라 `go get -u` 대상에서 제외된다. go 지시자(1.26.0)와
toolchain(go1.26.4) 은 변경하지 않았다.

검증 (go1.26.5 darwin/arm64, 전부 exit 0):
- go build ./...                 → exit 0
- go vet ./...                   → exit 0
- make lint (golangci-lint v2.11.4) → exit 0, "0 issues."
- make test (envtest k8s 1.36.2) → exit 0, 17 패키지 ok / FAIL 0
  internal/controller 53.1% · internal/webhook/v1alpha1 91.1% ·
  internal/resources 92.5% · internal/backuplifecycle·federation·migration 100%

변경 파일은 go.mod / go.sum 뿐이다 (make test 의 manifests·generate·fmt 는
추가 diff 를 만들지 않았다 = 생성물 drift 0).

Signed-off-by: phil <phil@keiailab.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@KeiaiLab-PHIL

Copy link
Copy Markdown
Contributor

PR #308(의존성 일괄 최신화, 머지됨)이 이 변경을 동일하거나 더 최신 버전으로 수렴시켜 superseded 되었습니다. go.mod/go.sum 실측 대조로 확인했습니다.

@dependabot @github

dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/go_modules/main/redis-7884a97628 branch July 20, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency updates go Go code or module changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant