Update all minor and patch updates - #50
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-and-patch-updates
branch
from
July 7, 2026 00:05
c4f9150 to
c679870
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/all-minor-and-patch-updates
branch
3 times, most recently
from
July 15, 2026 00:59
598cdf5 to
4dc7a2f
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-and-patch-updates
branch
from
July 20, 2026 20:22
4dc7a2f to
664b35a
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-and-patch-updates
branch
2 times, most recently
from
July 29, 2026 00:33
28d3e91 to
e956d0c
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/all-minor-and-patch-updates
branch
from
July 29, 2026 05:46
e956d0c to
ddf3338
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/all-minor-and-patch-updates
branch
from
July 30, 2026 20:42
ddf3338 to
7fc043c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v9.20.0→v9.21.0v2.6.0→v2.8.0Release Notes
redis/go-redis (github.com/redis/go-redis/v9)
v9.21.0Compare Source
v9.20.1: 9.20.1Compare Source
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
PeekPushNotificationNamepreviously inspected only the bytes already buffered bybufio, 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 andReadReplysilently 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
PeekPushNotificationNameno 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 @ndyakovFT.HYBRIDvector params: Vector data is now always sent viaPARAMSwith auto-generated param names (__vector_param_N, with collision avoidance) whenVectorParamNameis omitted, since Redis no longer accepts inline vector blobs; theFTHybridOptions.Paramsmap is no longer mutated, so the same options struct can be reused across calls (#3844) by @ndyakovCLUSTER SHARDSforward compatibility: Unknown shard- and node-level attributes in theCLUSTER SHARDSreply are now skipped viaDiscardNext()instead of erroring, so clients keep working when the server introduces new fields (#3843) by @madolsonPubSub.releaseConnno 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
mongodb/mongo-go-driver (go.mongodb.org/mongo-driver/v2)
v2.8.0: MongoDB Go Driver 2.8.0Compare Source
The MongoDB Go Driver Team is pleased to release version 2.8.0 of the official MongoDB Go Driver.
Release Highlights
This release supports the general availability of Queryable Encryption string queries. The query types
prefix,suffix, andsubstringare added as generally available for MongoDB 9.0+ and libmongocrypt 1.20.0. The query typesprefixPreview,suffixPreview, andsubstringPreviewremain experimental for 8.2–8.x servers and may be removed in a future release.Other key facts:
TextPreviewis replaced withString.options.Text()→options.String();TextOptions*→StringOptions*;EncryptOptionsBuilder.SetTextOptions→SetStringOptions.What's Changed
✨ New Features
📦 Dependency Updates
Full Changelog: mongodb/mongo-go-driver@v2.7.0...v2.8.0
For a full list of tickets included in this release, please see the list of fixed issues.
Documentation for the Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. For issues with, questions about, or feedback for the Go Driver, please look into our support channels, including StackOverflow. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go Driver is greatly appreciated!
v2.7.0: MongoDB Go Driver 2.7.0Compare Source
The MongoDB Go Driver Team is pleased to release version 2.7.0 of the official MongoDB Go Driver.
Release Highlights
This release adds support for sending afterClusterTime on writes in causally consistent sessions, improving alignment between read and write behavior in session-based workflows. It also continues cleanup of session-related and internal-only APIs by deprecating the experimental session API, helping clarify which surfaces are intended for long-term public use. Alongside that, the release includes a handful of targeted quality improvements across BSON validation, change streams, and error reporting to make the driver more predictable and easier to debug.
What's Changed
✨ New Features
🐛 Fixed
📝 Other Changes
New Contributors
Full Changelog: mongodb/mongo-go-driver@v2.6.2...v2.7.0
For a full list of tickets included in this release, please see the list of fixed issues.
Documentation for the Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. For issues with, questions about, or feedback for the Go Driver, please look into our support channels, including StackOverflow. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go Driver is greatly appreciated!
v2.6.2: MongoDB Go Driver 2.6.2Compare Source
The MongoDB Go Driver Team is pleased to release version 2.6.2 of the official MongoDB Go Driver.
Release Highlights
This release excludes non-I/O TLS errors from backpressure labels, aligning error labeling more closely with the CMAP specification. This fixes cases where protocol-level TLS handshake failures, such as certificate validation, hostname mismatch, fatal alerts, or malformed record headers, could be incorrectly classified as overload-related errors. As a result, these failures are handled more accurately during connection establishment and SDAM/pool error processing.
What's Changed
🐛 Fixed
Full Changelog: mongodb/mongo-go-driver@v2.6.1...v2.6.2
For a full list of tickets included in this release, please see the list of fixed issues.
Documentation for the Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. For issues with, questions about, or feedback for the Go Driver, please look into our support channels, including StackOverflow. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go Driver is greatly appreciated!
v2.6.1: MongoDB Go Driver 2.6.1Compare Source
The MongoDB Go Driver Team is pleased to release version 2.6.1 of the official MongoDB Go Driver.
Release Highlights
This release fixes batched writes to split by full wire-message size instead of document payload size, preventing near-limit InsertMany failures; fixes unmarshaling of null and undefined values into raw BSON types such as bson.Raw, bsoncore.Document, and bsoncore.Array; and fixes mongo.ErrorCodes() to return codes for ClientBulkWriteException, including duplicate-key errors from client bulk writes.
What's Changed
🐛 Fixed
New Contributors
Full Changelog: mongodb/mongo-go-driver@v2.6.0...v2.6.1
For a full list of tickets included in this release, please see the list of fixed issues.
Documentation for the Go Driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. For issues with, questions about, or feedback for the Go Driver, please look into our support channels, including StackOverflow. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go Driver is greatly appreciated!
Configuration
📅 Schedule: (in timezone America/Chicago)
* 10-18 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.