Repository navigation
fix(deps): update go-libraries - #6295
renovate-bot wants to merge 1 commit into
Conversation
ℹ️ Artifact update noticeFile name: bindings/go/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by Details:
File name: go/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by Details:
|
98262b5 to
cf056d7
Compare
ff611fa to
1a89a5f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6295 +/- ##
=======================================
Coverage 59.02% 59.02%
=======================================
Files 170 170
Lines 15870 15870
=======================================
Hits 9368 9368
Misses 6499 6499
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
1a89a5f to
ab9ca82
Compare
This PR contains the following updates:
v2.1.0→v2.1.1v1.27.1→v1.28.1v1.31.0→v1.32.1v2.7.0→v2.8.1v1.69.0→v1.70.0v5.11.0→v5.12.0v1.20.0→v1.20.1v2.1.6→v2.1.15v4.0.0-rc.6→v4.0.0v0.37.0→v0.38.0v0.24.0→v0.25.0v0.306.0→v0.311.0v1.84.0→v1.85.0v0.37.1→v0.37.2Release Notes
charmbracelet/bubbletea (charm.land/bubbletea/v2)
v2.1.1Compare Source
Terminal size query vulnerability
This patch version fixes a vulnerability reported by @Reload3d. You can find the details of the exploit here.
Best regards,
Charm XX 💫
Changelog
Fixed
9c6c325: fix: ingnore implausible terminal resize reports (#1887) (@andrinoff)Other stuff
67b4c7a: v2.1.1 (@andrinoff)Thoughts? Questions? We love hearing from you. Feel free to reach out on X, Discord, Slack, The Fediverse, Bluesky.
googleapis/google-cloud-go (cloud.google.com/go/datastore)
v1.28.1: datastore: v1.28.1Bug Fixes
v1.28.0: video: v1.28.0v1.28.0 (2026-04-02)
jackc/pgx (github.com/jackc/pgx/v5)
v5.12.0Compare Source
tidwall/gjson (github.com/tidwall/gjson)
v1.20.1Compare Source
yuin/goldmark (github.com/yuin/goldmark/v2)
v2.1.15Compare Source
v2.1.14Compare Source
v2.1.13Compare Source
v2.1.12Compare Source
v2.1.11Compare Source
v2.1.10Compare Source
v2.1.9Compare Source
v2.1.8Compare Source
v2.1.7Compare Source
yaml/go-yaml (go.yaml.in/yaml/v4)
v4.0.0: go-yaml v4.0.0Compare Source
go-yaml v4.0.0
go-yaml v4.0.0 is the first stable release of the v4 series, maintained by the
YAML organization.
It adds configurable loading and dumping, public plugin interfaces, structured
errors, and a CLI for inspecting YAML processing.
The classic APIs remain supported, so applications can adopt v4 incrementally.
Getting started
Install the release:
Use this import path in your Go code:
For an existing v3 application, start by updating imports, reviewing custom
unmarshalers, and running your tests.
You can continue using
Unmarshal,Marshal,NewDecoder, andNewEncoder.The v2 and v3 APIs remain frozen, with security fixes only; new features and
routine bug fixes are developed in v4.
Why add Load and Dump?
Applications need different YAML policies: strict configuration validation,
particular output layouts, or custom anchor handling.
The new
LoadandDumpfunctions and streamingLoaderandDumperacceptfunctional options and plugins for those choices.
They use YAML's load/dump terminology and are recommended for new code.
The classic entry points keep compatibility settings rather than changing
formatting and error presentation for every existing caller.
Moving to the new API is an explicit choice to use v4 defaults, with presets
available when you want older settings.
Classic APIs remain supported.
For example, load a configuration with strict field checking, then choose its
output indentation:
Unknown struct fields are ignored by default;
WithKnownFields()opts intorejecting them.
Duplicate mapping keys are rejected by default.
Options apply in order, so later options override earlier settings.
Defaults and compatibility
Quoting still depends on scalar content and styles, and line width is a
preference rather than a guaranteed maximum.
NewDecoderuses v3 error formatting;NewEncoderretains v3 output settingswith v4 error formatting.
Choose
WithV3Defaults()to select compatibility defaults through the new API.When replacing
Marshal, also disable wrapping to match its line-width setting:Presets select defaults; they do not reverse every v4 bug fix or reproduce every
legacy code path.
For example, package-level
Loadrequires exactly one document, whereasUnmarshalretains legacy handling of empty input and trailing content.WithSingleDocument()deliberately skips validation of later documents.Use
WithAllDocuments()to load or dump slices as document streams, or use astreaming loader or dumper to process documents individually.
Options, plugins, and nodes
Options control indentation, sequence layout, quoting, document markers,
Unicode escaping, field validation, and more.
OptsYAMLaccepts YAML configuration for supported settings, which can also beshared with the CLI.
The public plugin APIs cover six areas:
merge algorithm.
dotted paths, or reject alias references.
The core module provides implementations for these APIs.
Additional parsers live in separate modules, keeping their dependencies optional.
Existing depth and alias protections remain enabled by default.
yaml.Nodegives access to tags, styles, comments, anchors, and source positions.Node.LoadandNode.Dumpaccept options for node conversion.Pass construction options explicitly inside custom unmarshaler hooks;
Node.Loadstarts with fresh defaults independently of its calling loader.Stream nodes can expose encoding and YAML directives.
Node output retains supported styles and comments without promising identical
source formatting.
Migration details to check
NewLoaderandNewDumperreturn errors; check them before using the stream.Check dumper
DumpandCloseerrors as well.Custom
UnmarshalYAML(*yaml.Node) errorhooks must use the v4 node type.Recognized v3 node hooks produce a migration error rather than silently losing
custom behavior.
The legacy
UnmarshalYAML(func(any) error) errorcallback remains supported.Conversion failures return structured
*yaml.LoadErrorsvalues.Use
errors.Asto inspect structured errors or match legacy*yaml.TypeErrorvalues, rather than relying on a direct type assertion or fixed message text.
Review the migration guide
for the complete compatibility guidance.
Inspect YAML with the CLI
Install the CLI from this release:
Convert to JSON, inspect nodes, or examine scanner and parser output:
The CLI also supports reusable options files and pipelines between intermediate
stages, making small bug reports easier to reproduce.
Runtime plugin selection chooses implementations already linked into the binary.
Further reading and thanks
See the options guide,
plugin guide,
CLI guide,
and API reference.
Please report problems with minimal input, a reproducer, and your Go version in
the issue tracker.
Release-candidate users should update to v4.0.0 and rerun their tests, as some APIs
changed during prerelease development.
Thanks to everyone who tested, reported problems, and contributed to this release.
v4.0.0-rc.9Compare Source
v4.0.0-rc.8Compare Source
v4.0.0-rc.7Compare Source
googleapis/google-api-go-client (google.golang.org/api)
v0.311.0Compare Source
Features
v0.310.0Compare Source
Features
v0.309.0Compare Source
Features
v0.308.0Compare Source
Features
v0.307.0Compare Source
Features
grpc/grpc-go (google.golang.org/grpc)
v1.85.0: Release 1.85.0Compare Source
New Features
:authorityheader) in clientstats.OutHeaderevents. (#9296)ValueFromOutgoingContext, which reads a single metadata value from outgoing context without copying the entire outgoing metadata into a new map. (#9282)Bug Fixes
GRPC_GO_EXPERIMENTAL_CONTROL_BUFFER_THROTTLE_LIMITfrom 100 to 10,000, and close client connections if reads remain throttled for10s. (#9563)Stop()forcefully terminates the server whileGracefulStop()is waiting for active handlers to complete. (#9394)HEADERSframes to comply with RFC 7540 §5.1.1. Previously, truncatedHEADERSframes left the connection in an inconsistent state and allowed stream IDs to be reused by clients without resulting in a protocol error. (#9414)HEADERSframe includes theEndStreambit. Previously, this caused server handlers to hang when reading a message. (#9391):authorityandHostheaders with HTTP 400 and statusInternal. (#9365):authorityvalue specified by the LB policy instead of inheriting it from a previous attempt. (#9277)io.ErrUnexpectedEOFinstead ofio.EOFupon receiving truncated message headers or bodies after partial data has already been received. (#9204)kubernetes/apimachinery (k8s.io/apimachinery)
v0.37.2Compare Source
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.