fix(deps): update vulnfeeds-go#5543
Open
renovate-bot wants to merge 1 commit into
Open
Conversation
forking-renovate
Bot
added
the
dependencies
ℹ️ Artifact update noticeFile name: vulnfeeds/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate-bot
force-pushed
the
renovate/vulnfeeds-go
branch
5 times, most recently
from
418383f to
1474a7d
Compare
renovate-bot
force-pushed
the
renovate/vulnfeeds-go
branch
from
1474a7d to
29ad86b
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
1 participant
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:
v2.0.3→v2.0.4v1.62.2→v1.62.3v1.32.0→v1.33.0v2.5.1→v2.5.2v9.20.0→v9.20.1v0.20.0→v0.21.0v0.37.0→v0.38.0v0.283.0→v0.284.0Release Notes
charmbracelet/lipgloss (charm.land/lipgloss/v2)
v2.0.4Compare Source
Mini Crash Patch
Hi! This is a small patch to fix a writer-related panic. Thanks for using Lip Gloss!
Changelog
Fixed
fefa41d: fix: prevent crash when writing to a closed wrap writer (#699) (@taciturnaxolotl)Docs
40ec0e6: docs: fix typo in table comment (#641) (@aymanbagabas)a4d0b40: docs: restore missing diaereses (#664) (@meowgorithm)Chore
aa91b99: chore: remove CODEOWNERS (@aymanbagabas)9cbfe8b: chore(lint): exclude revive naming linter (@aymanbagabas)Thoughts? Questions? We love hearing from you. Feel free to reach out on X, Discord, Slack, The Fediverse, Bluesky.
JohannesKaufmann/html-to-markdown (github.com/JohannesKaufmann/html-to-markdown/v2)
v2.5.2Compare Source
Changelog
290df46add FAQ for character encoding61d55bdremove firecrawl banner19162a2update versionredis/go-redis (github.com/redis/go-redis/v9)
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
googleapis/google-api-go-client (google.golang.org/api)
v0.284.0Compare Source
Features
Configuration
📅 Schedule: (in timezone Australia/Sydney)
🚦 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.