Skip to content

chore(deps): bump the go-minor-and-patch group across 1 directory with 6 updates - #6

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/go-minor-and-patch-1ceea1704b
Closed

chore(deps): bump the go-minor-and-patch group across 1 directory with 6 updates#6
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/go-minor-and-patch-1ceea1704b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 26, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the go-minor-and-patch group with 6 updates in the / directory:

Package From To
github.com/modelcontextprotocol/go-sdk 1.6.1 1.8.0
modernc.org/sqlite 1.46.1 1.59.0
github.com/redis/go-redis/v9 9.7.3 9.14.1
google.golang.org/grpc 1.83.1 1.84.0
github.com/wneessen/go-mail 0.7.2 0.8.1
github.com/nats-io/nats.go 1.53.1 1.54.0

Updates github.com/modelcontextprotocol/go-sdk from 1.6.1 to 1.8.0

Release notes

Sourced from github.com/modelcontextprotocol/go-sdk's releases.

v1.8.0

This release is equivalent to v1.8.0-pre.2. Thank you to those who tested the pre-release.

In this release we introduce several fixes and improvements on top of v1.7.0. It adds no new protocol revision: the supported set is unchanged, and 2026-07-28 remains the newest version the SDK negotiates.

The bulk of the work is hardening the transports against resource exhaustion, closing session leaks, deadlocks and teardown hangs found by users running the new protocol at scale, and giving servers explicit control over which protocol versions they advertise.

Two behavior changes are guarded by new MCPGODEBUG flags; see the section below.

Hardening against resource exhaustion

Every decoding path that buffers incoming input is now bounded. JSON payloads are rejected past 1000 levels of nesting, before the parser recurses. Both SSE readers cap the bytes buffered for a single event via MaxEventSize on SSEClientTransport and StreamableClientTransport, and the stdio transport caps a single JSON-RPC frame via StdioTransport.MaxLineLength.

On the OAuth side, dynamic client registration responses are bounded to 1 MB, and the discovery code now validates metadata documents rather than trusting them.

Restricting the protocol versions a server supports

ServerOptions.SupportedProtocolVersions lets a server narrow the set of versions it advertises and negotiates. The list can only narrow, never widen; naming a version the SDK does not implement panics at construction. Relatedly, a stateful streamable handler receiving a 2026-07-28 request now returns that same JSON-RPC error instead of a plain-text 400, so the client can renegotiate down instead of losing the connection.

Per-request cache control

ServerOptions.SetCacheable is a new hook that decides the ttlMs and cacheScope fields of every result carrying them: server/discover, the four list methods, and resources/read. It runs once per result, after the handler returns, with the values that handler produced, so it can set a policy globally while still letting an individual handler override it. Anything left unset falls back to the protocol default of public.

Behavior changes guarded by MCPGODEBUG

Two new escape-hatch flags restore the previous behavior of the changes above. Both will be removed in v1.9.0.

  • plaintextstatefulrejection=1 — restore the plain-text http.Error 400 body a stateful StreamableHTTPHandler previously returned for a request carrying per-request metadata. The default is now a JSON-RPC -32022 CodeUnsupportedProtocolVersion error with an UnsupportedProtocolVersionData payload advertising the legacy versions the server supports. Introduced by #1143.
  • blockingcancelnotify=1 — restore the previous behavior where a cancelled call waits synchronously for notifications/cancelled to be delivered (up to 5s) before returning, joining any delivery error into the caller's error. The default now retires the call immediately and sends the notification asynchronously. Introduced by #1151.

Options below were removed, according to plan:

  • seterroroverwrite
  • enableoriginverification
  • disablecontenttypecheck

... (truncated)

Commits
  • 3f3b699 refactor: remove legacy MCPGODEBUG compatibility for new protocol release (#1...
  • 830f0b7 mcp: update conformance tests (#1231)
  • 12cbafe oauthex: oauth discovery checks (#1220)
  • 3632967 mcp: add an sse event size cap (#1205)
  • 0d3036f mcp: allow per request Cacheable customization (#1203)
  • cb0de64 mcp: add a max request body size of the old transport (#1224)
  • 2fdabde mcp: do not check metatada on notifications (#1215)
  • 59185e6 build(deps): bump ossf/scorecard-action from 2.4.3 to 2.4.4 (#1217)
  • a6764cf build(deps): bump golang/govulncheck-action from 1.0.4 to 1.1.0 (#1218)
  • 8227246 fix: only subscribe when server advertises capability (#1221)
  • Additional commits viewable in compare view

Updates modernc.org/sqlite from 1.46.1 to 1.59.0

Changelog

Sourced from modernc.org/sqlite's changelog.

Changelog

Entries for v1.38.1 through v1.44.1 and for v1.49.1 were added on 2026-09-05, reconstructed from the git history and the merge requests they cite; they were missing at release time.

  • 2026-09-15 v1.59.1:

    • make vendor now writes vendor.json: the modernc.org/libsqlite3 and modernc.org/libsqlite_vec commits and the Go toolchain lib/ and vec/ were vendored with, so git show vX.Y.Z:vendor.json says which revisions a release carries. It refuses a dirty sibling checkout, siblings on different modernc.org/libc versions, or a libsqlite_vec built against another libsqlite3. The suite fails when lib/, vec/ or the libc in go.mod no longer match the stamp, so a libc bump goes in the same push as make vendor. Tooling only; the vendored code is unchanged. See [GitLab merge request #140](https://gitlab.com/cznic/sqlite/-/merge_requests/140).
    • vfs.FS.Close now refuses while a database opened through it is still open, returning an error that wraps the new vfs.ErrInUse and leaving the VFS registered. It used to free the VFS the open connection still called through, so the next query crashed the process or read through freed memory. Close the databases first, then the FS.
    • Fix handle reuse in modernc.org/sqlite/vfs on 32-bit targets: after 2^32 file opens in one process the handle counter wrapped and could overwrite a live entry, such as a file system registered at start-up, and crash. 64-bit targets were not affected.
    • The pluggable page cache now panics when a Cache breaks its contract by returning nil, or a different Page, from Fetch for a page SQLite still holds pinned. It used to free memory SQLite was still using, corrupting the database without an error. Only a Cache implementation with that bug is affected; modernc.org/sqlite/pcache is not.
    • Document three limits of the pluggable page cache: a program importing modernc.org/sqlite/vec cannot call RegisterPageCache (it fails with SQLITE_MISUSE), PageCache.Create may be called concurrently, and under cache=shared a Cache is called from several goroutines, serialized by SQLite, so it wants a mutex of its own to run clean under -race. Documentation only.
    • Document two properties of connections in the package documentation: state set on a pooled connection -- PRAGMAs set with Exec, ATTACHed databases, temporary tables, anything registered through sql.Conn.Raw -- is inherited by the next caller to borrow it, and a driver connection reached through Raw is not safe for concurrent use even though every connection is opened SQLITE_OPEN_FULLMUTEX. Documentation only.
    • Add StrictPragmas, opt-in and off by default: once enabled, a connection whose _pragma DSN value holds more than one SQL statement fails to open with ErrMultiStatementPragma, before any DSN parameter is applied. A _pragma value runs as SQL text, so _pragma=foreign_keys(1);ATTACH 'x.db' AS x also attaches, and creates, x.db; the Driver.Open documentation said "a PRAGMA statement" and now says what actually happens. Enabling it is recommended for any application whose DSN is not a compile-time constant.
    • Document SQLite's own URI query parameters on Driver.Open: mode, cache, immutable, nolock, psow and modeof. Every connection is opened with SQLITE_OPEN_URI, so in a DSN starting with file: these have always worked; only the driver's own keys were listed. The docstring also spells out the trap that a plain file name has its query stripped before SQLite sees it, so /path/to.db?mode=ro opens read-write. Documentation only.
    • Resolves [GitLab issue #257](https://gitlab.com/cznic/sqlite/-/issues/257).
    • Add IRP.md, an incident response plan: who runs a response when there are two maintainers in different time zones, how a report is scoped across the three layers this module is built from, the fix path for each, and what to do when a released version is itself the problem -- a published Go module version cannot be recalled, so retract plus a new release is the remedy. Linked from SECURITY.md. Documentation only.
    • Add CONTRIBUTING.md: where to send a merge request, which files are generated and must not be edited by hand, how to build and test across the 20 supported targets, and the AUTHORS/CONTRIBUTORS convention. Contribution guidance previously existed only in GOVERNANCE.md and HACKING.md, neither of which a first-time contributor is likely to open. Documentation only.
    • Add SECURITY.md: report a vulnerability through GitHub private vulnerability reporting, a confidential GitLab issue, or the project's Service Desk address, never a public issue. It states what is in scope -- including transpilation faults, where the generated Go does not faithfully implement the C it came from -- that only the latest release is supported, and that a confirmed report is disclosed through a GitHub advisory, an entry in the Go vulnerability database so govulncheck reports it, and a release note. Documentation only.
    • Ship a Software Bill of Materials: sbom.cdx.json (CycloneDX 1.6) and sbom.spdx.json (SPDX 2.3), both validated against the published schemas, with SBOM.md explaining what they cover. They name what an SBOM built from the module graph cannot see -- the transpiled SQLite 3.53.4 and sqlite-vec C, and the upstreams modernc.org/libc vendors, musl among them -- and mark every component as linked into your binary, test-only, or compiled into nothing. Documentation only.
    • Ship LICENSE-3RD-PARTY.md, a transitively flattened inventory of every third-party component this module carries: the whole Go module graph, the transpiled SQLite and sqlite-vec C that no go.mod names, and the upstreams modernc.org/libc carries in turn, musl among them. It reproduces all seventeen distinct license texts in full and separates what is linked into your binary from what only appears in the module graph. The LICENSE name prefix is what makes go mod vendor carry it into downstream vendor/ trees. Documentation only.

  • 2026-09-15 v1.59.0:

    • Bump the pinned modernc.org/libc to v1.75.7 and re-vendor lib/ and vec/. The transpiled SQLite is unchanged, still 3.53.4. On the Linux targets the new libc replaces transpiled musl memcpy, memmove, memset, memcmp and strlen with native Go, cutting CPU time on query-heavy workloads by up to a third; see the new Performance section below. As always, downstream go.mod files must pin the same modernc.org/libc version this repository's go.mod does; see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
    • Hand user-defined function and aggregate callbacks a pooled *FunctionContext instead of allocating a fresh one per call, removing the last driver-side allocation per invocation. Like the argument slice, it is valid only for the duration of the callback and must not be retained past its return. Updates [GitLab issue #226](https://gitlab.com/cznic/sqlite/-/issues/226). See [GitLab merge request #137](https://gitlab.com/cznic/sqlite/-/merge_requests/137).
    • Add regression tests pinning the identity and the pooling of that context. See [GitLab merge request #138](https://gitlab.com/cznic/sqlite/-/merge_requests/138), thanks Ian Chechin!
    • Add a Performance section to the package documentation: measured CPU-time ratios of this driver against the same SQLite compiled from C, where the gap comes from, and the two consequences for applications — index the columns that ORDER BY, GROUP BY and WHERE use, and bound the database/sql pool with SetMaxOpenConns.

  • 2026-09-01 v1.58.0:

    • Upgrade to SQLite 3.53.4. It carries upstream's own fix for the journal-rollback data-corruption bug, so the local super-journal patch v1.56.0 introduced is dropped; recovery behavior is unchanged. Also bumps the pinned modernc.org/libc to v1.75.6; as always, downstream modules must pin the same version this one does, see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
    • Add opt-in support for Linux Open File Description (OFD) locks on database files, off by default; without opting in, locking behavior is byte-for-byte that of previous releases. A POSIX record lock is owned by the (process, inode) pair, so any Close of any descriptor of the database file anywhere in the process silently strips SQLite's locks; OFD locks survive that. Enable it process-wide with MODERNC_SQLITE_OFD_LOCK=1 in the environment, or with the new OFDLocking(true) before the first connection is opened; OFDLockingEnabled reports the mode in effect, and the new ErrOFDLockingTooLate and ErrOFDLockingUnavailable report a switch attempted too late and a platform or filesystem without the feature. Why it is process-wide rather than a DSN parameter, what WAL's -shm coordination still uses, and the /proc/locks measurements behind the design are in [GitLab issue #255](https://gitlab.com/cznic/sqlite/-/issues/255).
    • Resolves [GitLab issue #255](https://gitlab.com/cznic/sqlite/-/issues/255). See [GitLab merge request #136](https://gitlab.com/cznic/sqlite/-/merge_requests/136), thanks Nathan Herring (@​technosloth), and thanks Gani Georgiev (@​ganigeorgiev) for pressing the opt-in default!

  • 2026-08-19 v1.57.0:

    • Add an opt-in _defensive DSN query parameter turning on SQLite's defensive mode for the connection. On such a connection PRAGMA writable_schema=ON, PRAGMA journal_mode=OFF and PRAGMA schema_version=N become silent no-ops, and writes to a virtual table's shadow tables and to sqlite_dbpage fail. It is a hardening measure, not a sandbox for hostile database files, for which it is only one of the steps SQLite recommends, and it is a property of the connection, not of the file. Absent, or _defensive=0, nothing changes.
    • Reject _defensive=1 together with _journal_mode=OFF (or _journal=OFF) instead of opening a connection in which neither was honoured: SQLite turns that PRAGMA into a no-op that still reports success. Only DSNs using the new parameter can be affected. See [GitHub pull request #6](modernc-org/sqlite#6), thanks wsman!
    • Ship the sqlite-vec license notice this module has been missing since vec/ arrived in v1.47.0. sqlite-vec is Copyright (c) 2024 Alex Garcia, dual-licensed Apache-2.0 OR MIT and used here under MIT; the text now ships as LICENSE-SQLITE_VEC, and make vendor fails rather than quietly dropping it.
    • The SQLite notice is renamed from SQLITE-LICENSE to LICENSE-SQLITE; update any direct links to it. Its contents are unchanged. The rename is what makes go mod vendor carry both notices into downstream vendor/ trees: it selects license files by name prefix, so a name merely ending in LICENSE was never propagated.
    • Let a caller-constructed Driver register its own functions, collations and virtual table modules, through new RegisterFunction, RegisterScalarFunction, RegisterDeterministicScalarFunction, RegisterCollationUtf8 and RegisterModule methods plus Must* variants, and let vtab.RegisterModule honour its db argument. Behavior change: vtab.RegisterModule(db, ...) where db was opened on a caller-constructed Driver used to discard db and land on the registered sqlite driver, reaching every connection in the process; it now lands on that Driver alone, so a sql.Open("sqlite") connection that used to resolve such a module gets no such module. Everything else is additive, and the isolating change discussed in [GitLab issue #254](https://gitlab.com/cznic/sqlite/-/issues/254) is deliberately not made here. See [GitLab merge request #135](https://gitlab.com/cznic/sqlite/-/merge_requests/135), thanks Ian Chechin!
    • Promote freebsd/386, freebsd/arm and netbsd/amd64 from experimental to fully supported. The package documentation's platform table had carried seventeen entries while this module shipped, cross-built and tested twenty; all three have been in the builder matrix since v1.53.0 and pass the full suite on this release's commit. Documentation only — lib/ is byte-for-byte what v1.56.0 shipped.

  • 2026-08-03 v1.56.0:

    • Re-vendor the transpiled sources, picking up modernc.org/libsqlite3's patch for an upstream data-corruption bug in SQLite 3.53.3's journal rollback. A crash during the commit of a multi-database (ATTACH) transaction can leave a hot journal whose zeroed super-journal name still validates, so pager_playback() deletes it without playing it back and leaves the database corrupted. Not a transpilation artifact: a plain gcc build of stock 3.53.3 fails on the same bytes. The SQLite version is unchanged at 3.53.3, every supported target carries the patch, and it will be dropped once upstream ships its own fix.
    • Two targets change beyond that patch. linux/s390x now allocates C bit-fields MSB-first as the big-endian ABI requires, from modernc.org/cc/v4 v4.29.1. linux/riscv64 was regenerated on a host running GCC 11.4.0 rather than 13.3.0, which drops some unreferenced compiler-predefined macro constants and changes what PRAGMA compile_options reports; no SQLite code generation differs. Every other target is byte-identical to v1.55.0 apart from the patch above.
    • Bump the pinned modernc.org/libc to v1.74.4 and the remaining dependencies to their current releases. v1.74.2 and v1.74.3 are retracted upstream over a freeaddrinfo lock leak that deadlocks name resolution, and v1.74.4 is the fix. As always, downstream modules must pin the same modernc.org/libc version this one does, see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
    • Add NewConnector, returning a database/sql/driver.Connector for use with sql.OpenDB. It opens the same connections sql.Open("sqlite", dsn) does, from the same registered driver, so every function, collation, connection hook and virtual table module registered through this package applies to them. It exists for callers that need to interpose on the physical connections database/sql opens — tracing, metrics, connection-scoped setup — for which the alternative was sql.Register, which is process-global, panics on a repeated name and cannot be undone. A runnable sample is in examples/connector. Resolves [GitLab issue #253](https://gitlab.com/cznic/sqlite/-/issues/253), thanks Alessandro Segala (@​ItalyPaleAle)!
    • Documentation sweep. openbsd/amd64 and openbsd/arm64 join the supported platforms table, the vfs DSN query parameter is documented alongside the others on Driver.Open, the stale go generate and GO_GENERATE instructions are replaced by modernc.org/libsqlite3 and make vendor, and vec and vfs gained the package doc comments they were missing. A caller-constructed sqlite.Driver is now documented as not being the driver this package registers as "sqlite": it carries none of the package-level functions and collations, so it can evaluate upper(x) or date(x) differently. Documentation only.

  • 2026-07-20 v1.55.0:

    • Add github.com/mattn/go-sqlite3-compatible shorthand DSN query parameters to ease migration from that driver: _busy_timeout/_timeout, _foreign_keys/_fk, _journal_mode/_journal, _synchronous/_sync, _auto_vacuum/_vacuum and _query_only, each setting the correspondingly named PRAGMA. Values are validated against the same set mattn/go-sqlite3 accepts and an unrecognized one fails the connection, so a typo cannot silently downgrade durability. Review DSNs carried over from that driver before upgrading: a key prior releases ignored entirely now takes effect, so _foreign_keys=on begins enforcing constraints and _journal_mode=wal persistently converts the file; and a duration-style _busy_timeout=5s now fails an open that previously succeeded. See [GitLab merge request #134](https://gitlab.com/cznic/sqlite/-/merge_requests/134), thanks Toni Spets (@​beeper-hifi) and Ian Chechin!
    • Validate every DSN query parameter before applying any of them. Parameters were checked as each was reached, so a DSN rejected for a later parameter had already executed the PRAGMAs ahead of it: file:x.db?_journal_mode=wal&_synchronous=bogus failed the connection and yet left x.db converted to WAL. A failed Open now leaves the database as it found it. The accepted values are unchanged. _pragma remains the sole exception, since its values are executed verbatim and can only be rejected by SQLite as they run.

  • 2026-07-15 v1.54.0:

... (truncated)

Commits
  • c96a4e6 CHANGELOG.md: document the libc v1.75.7 bump and the Performance section
  • 35c446e update dependencies, make vendor
  • 9ad02ac Merge branch 'udf-context-tests' into 'master'
  • d6d84a9 sqlite: pin the identity and the pooling of the FunctionContext in tests
  • 59ec397 doc.go: add a Performance section with measured driver-vs-C ratios
  • 51cbcbf Merge branch 'udf-call-pool' into 'master'
  • e390a0c sqlite: pool the FunctionContext handed to UDF and aggregate callbacks
  • 38af581 doc.go, README.md: point readers at CHANGELOG.md
  • 37e55e4 CHANGELOG.md: reconstruct the missing entries for v1.38.1 through v1.44.1 and...
  • 2f7234f AUTHORS, CONTRIBUTORS: add Nathan Herring; CHANGELOG.md: credit him by name
  • Additional commits viewable in compare view

Updates github.com/redis/go-redis/v9 from 9.7.3 to 9.14.1

Release notes

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

9.14.1

Changes

  • fix(otel): Add support for filtering traces for certain commands (#3519)
  • fix(pool): remove conn from idleConns if present (#3546)

Contributors

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

@​Sovietaced, @​ndyakov

9.14.0

Highlights

  • Added batch process method to the pipeline (#3510)

Changes

🚀 New Features

  • Added batch process method to the pipeline (#3510)

🐛 Bug Fixes

  • fix: SetErr on Cmd if the command cannot be queued correctly in multi/exec (#3509)

🧰 Maintenance

  • Updates release drafter config to exclude dependabot (#3511)
  • chore(deps): bump actions/setup-go from 5 to 6 (#3504)

Contributors

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

@​elena-kolevska, @​htemelski-redis and @​ndyakov

9.13.0

Highlights

  • Pipeliner expose queued commands (#3496)
  • Ensure that JSON.GET returns Nil response (#3470)
  • Fixes on Read and Write buffer sizes and UniversalOptions

Changes

  • Pipeliner expose queued commands (#3496)
  • fix(test): fix a timing issue in pubsub test (#3498)
  • Allow users to enable read-write splitting in failover mode. (#3482)
  • Set the read/write buffer size of the sentinel client to 4KiB (#3476)

🚀 New Features

  • fix(otel): register wait metrics (#3499)
  • Support subscriptions against cluster slave nodes (#3480)

... (truncated)

Changelog

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

9.14.1 (2025-10-15)

Changes

  • fix(otel): Add support for filtering traces for certain commands (#3519)
  • fix(pool): remove conn from idleConns if present (#3546)

Contributors

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

@​Sovietaced, @​ndyakov

9.14.0 (2025-09-10)

Highlights

  • Added batch process method to the pipeline (#3510)

Changes

🚀 New Features

  • Added batch process method to the pipeline (#3510)

🐛 Bug Fixes

  • fix: SetErr on Cmd if the command cannot be queued correctly in multi/exec (#3509)

🧰 Maintenance

  • Updates release drafter config to exclude dependabot (#3511)
  • chore(deps): bump actions/setup-go from 5 to 6 (#3504)

Contributors

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

@​elena-kolevska, @​htemelski-redis and @​ndyakov

9.13.0 (2025-09-03)

Highlights

  • Pipeliner expose queued commands (#3496)
  • Ensure that JSON.GET returns Nil response (#3470)
  • Fixes on Read and Write buffer sizes and UniversalOptions

Changes

  • Pipeliner expose queued commands (#3496)
  • fix(test): fix a timing issue in pubsub test (#3498)
  • Allow users to enable read-write splitting in failover mode. (#3482)
  • Set the read/write buffer size of the sentinel client to 4KiB (#3476)

... (truncated)

Commits
  • 512579f chore(release): bump version to 9.14.1 (#3548)
  • c699a45 fix(pool): remove conn from idle conns if present (#3546)
  • 33c70b2 fix: pipeline repeatedly sets the error (#3525)
  • 7706f88 Add support for filtering traces for certain commands (#3519)
  • 2da6ca0 chore(release): Update the rest of the versions (#3513)
  • c11a704 chore(release): v9.14.0 (#3512)
  • 8f5469a chore(ci): Update release drafter config to exclude dependabot (#3511)
  • a264ffb fix: SetErr on Cmd if the command cannot be queued correctly in multi/exec (#...
  • e0853ab Added batch process method to the pipeline (#3510)
  • 65e1c22 chore(deps): bump actions/setup-go from 5 to 6 (#3504)
  • Additional commits viewable in compare view

Updates google.golang.org/grpc from 1.83.1 to 1.84.0

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.84.0

Behavior Changes

  • stats/otel: The grpc.lb.pick_first.* metrics have been removed and replaced with grpc.subchannel.* metrics. See gRFC A94 for more details. (#9215)

New Features

  • xds: Add support for contains_match in route header matchers. (#9223)

Bug Fixes

  • client: Fix a bug where a ClientConn could get permanently stuck in IDLE when an RPC was canceled during stream creation. Previously, such cancellations triggered stream cleanup twice, corrupting the channel's idleness state and causing subsequent RPCs to fail with deadline exceeded errors. (#9191)
  • client: Fix a bug where non-gRPC HTTP responses ending with an empty DATA frame failed the RPC with status code Internal instead of preserving the HTTP-mapped status code and response body. (#9217)
  • credentials: Validate metadata returned by per-RPC credentials, failing the RPC with status code Internal if invalid keys or values are found. Previously, invalid metadata from credentials was sent to the server in outgoing HTTP/2 requests. (#9202)
  • credentials/sts: Prevent potential token leakage by disallowing HTTP redirects during STS token exchange. Previously, 3xx redirects were followed automatically, replaying the request body containing authentication tokens to the redirect destination. (#9299)
  • randomsubsetting: Ignore endpoints that contain no addresses. Previously, this could cause the policy to panic while computing hashes. (#9259)
  • stats/otel: Ensure method names are populated in trace spans when metrics are disabled. Previously, running with tracing enabled and metrics disabled resulted in server trace spans lacking the RPC method name (recording only "Recv."). (#9262)
  • transport: Return io.ErrUnexpectedEOF when EOF is encountered after partial header or message body reads. Previously, partial reads could return a plain io.EOF, failing to distinguish truncated data from a clean end of stream. (#9204)
  • transport: Validate metadata supplied by balancers (in PickResult.Metadata) and resolver addresses, failing the RPC with status code Internal if invalid keys or values are found. Previously, invalid metadata from these sources was sent to the server in outgoing HTTP/2 requests. (#9203)
  • xds: Fix a rare corner case that could prevent a cluster from being removed when it is no longer in use. (#9140)
  • xds: Fix panic during route matching for routes containing header matchers with empty exact_match strings. (#9223)
  • xds: Reject routes containing header matchers with empty prefix_match or suffix_match strings. Previously, this caused a panic during route matching. (#9223)
  • xds: Fix EDS drop policies being applied at a much lower rate than configured due to an integer overflow. (#9257)
  • xds: Reject EDS resources containing drop policies with unsupported denominators. Previously, such resources caused the client to panic when calculating drop rates. (#9218)
  • xds/rbac: Reject RBAC configurations containing nested Principal or Permission rules with :scheme or grpc- prefixed header matchers. Previously, such configurations could cause DENY policies to fail open. (#9258)
  • xds/rbac: Rewrite host header matchers to :authority in nested Principal and Permission rules. Previously, this rewrite only applied to top-level rules, causing nested host matchers to never match incoming requests and DENY policies to fail open. (#9258)
  • xds/rbac: Reject CidrRanges with an unset prefix length. Previously, an omitted prefix_len field caused a panic during RBAC configuration parsing. (#9250)

Performance Improvements

  • transport: Avoid a heap allocation when flushing shared write buffers. (#9233)
  • credentials/alts: Support dynamic frame size negotiation and add the GRPC_GO_EXPERIMENTAL_ALTS_MAX_FRAME_SIZE environment variable (default 4KiB, max 512KiB) to configure the maximum ALTS record frame size. (#9268)

Release 1.83.2

... (truncated)

Commits

Updates github.com/wneessen/go-mail from 0.7.2 to 0.8.1

Release notes

Sourced from github.com/wneessen/go-mail's releases.

v0.8.1

Welcome to go-mail v0.8.1! 🎉

This release is only a small release, but fixes a regression on the 386 platform. We hope you enjoy!

Notable features / improvements / fixes

Fix regression on 386 platforms

The NTLM support introduced in v0.8.0 contained a bug affecting 386 platforms: a 32-bit integer could overflow because it wasn't cast to int64. This caused problems when cross-compiling to the 386 architecture. The bug is fixed in #589. In addition, the CI pipeline has been extended to run cross-compile tests for every platform supported by GitHub runners. Thanks to @​firefart for reporting the issue.

Opportunistic SMTP authentication

PR #585 introduces an opportunistic authentication mechanism that lets users provide a list of preferred auth types. During SMTP authentication, the client checks the mechanisms the server supports and selects the first match from the preferred list. If the server supports none of the preferred mechanisms, the client falls back to Autodiscover mode and selects the strongest mechanism the server offers.

Convenience helpers for List-Unsubscribe and one-click List-Unsubscribe-Post

We already expose the HeaderListUnsubscribe and HeaderListUnsubscribePost header constants, but until now there was no dedicated function to construct these headers. Users had to assemble the angle-bracket URI list and the exact List-Unsubscribe=One-Click token by hand via SetGenHeader—something that's easy to get subtly wrong (missing <>, an incorrect POST token, or GET-triggerable URLs). Since February 2024, Gmail and Yahoo require a working RFC 8058 one-click unsubscribe for senders exceeding 5k messages per day, making this a common compliance requirement rather than a niche feature. PR #587 adds three convenience helpers to set these headers correctly:

  • SetListUnsubscribe(uris ...string): sets an RFC 2369 List-Unsubscribe header only (mailto/https links).
  • SetListUnsubscribePost(): sets List-Unsubscribe-Post: List-Unsubscribe=One-Click.
  • SetListUnsubscribeOneClick(httpsURL string, additionalURIs ...string): the common case: sets both headers correctly, validating that at least one HTTPS URL is present as required by RFC 8058.

What's Changed

CI/CD maintenance changes

Full Changelog: wneessen/go-mail@v0.8.0...v0.8.1

v0.8.0: Native NTLM and DKIM support

Welcome to go-mail v0.8.0! 🎉

This release brings two big new features and a couple of improvements and fixes to go-mail. We hope you enjoy this release!

[!IMPORTANT] This release adds a new dependency to go.mod. We now rely on the crypto package of the Go extended library. We already relied on golang.org/x/text before, but it's worth noting that if you have strict dependency requirements, that golang.org/x/crypto was added in this release.

Notable features/improvements/fixes

Native NTLM authentication support

With PR #576 native NTLMv2 SMTP auth support has been added to go-mail. This feature has been requested several times and so far we've always resorted to a custom SMTP authentication provider using some 3rd party libraries. With go-mail v0.8.0 you can now natively authenticate with NTLM servers like any of the other supported authentication methods. Big thanks to @​mkalus for providing some ground work in #549 and for helping to test the code. The development was mainly based on the excellent documentation of the cURL project.

... (truncated)

Commits
  • 2ac36f0 Update doc.go
  • 1550ad6 Merge pull request #598 from wneessen/churn/ci-cd-crosscompile
  • 896ceb6 Fix linux/386
  • 80296ec Add linux 386
  • 7f544b1 Only execute cross compile tests we can actually use
  • 47f7a74 Enable CGO
  • f3ab24e Add cross-compile test to CI
  • a0f7cbe Merge pull request #597 from wneessen/dependabot/go_modules/golang.org/x/cryp...
  • 86f6131 Bump golang.org/x/crypto from 0.53.0 to 0.54.0
  • 2b6e523 Merge pull request #592 from wneessen/dependabot/github_actions/github/codeql...
  • Additional commits viewable in compare view

Updates github.com/nats-io/nats.go from 1.53.1 to 1.54.0

Release notes

Sourced from github.com/nats-io/nats.go's releases.

Release v1.54.0

Changelog

This release raises the minimum supported Go version to 1.26 and adds support for nats-server v2.15 stream and consumer info fields.

ADDED

  • Core NATS:
    • nats.MultipathTCP() option to enable or disable MPTCP for outbound connections (#2145)
    • Conn.ConnectedDomain() to read the JetStream domain advertised by the connected server (#2139)
  • JetStream:
    • ClusterInfo.Desired, PeerInfo.Peer, PeerInfo.Pending and StreamSourceInfo.Seq in stream and consumer info, reported by nats-server v2.15 (#2144)
    • Nats-Schedule-Rollup header const and WithScheduleRollup() publish option (#2142)

FIXED

  • Core NATS:
    • Panic in DecodeHeadersMsg on inline status tokens shorter than 3 characters. Thanks @​nikitha-m for the contribution (#2101)
    • Data race on Subscription.sid between applyNewSID and removeSub (#2122)
  • JetStream:

@dependabot
chore(deps): bump the go-minor-and-patch group across 1 directory wit…
ec55e0c 
…h 6 updates

Bumps the go-minor-and-patch group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [github.com/modelcontextprotocol/go-sdk](https://github.com/modelcontextprotocol/go-sdk) | `1.6.1` | `1.8.0` |
| [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) | `1.46.1` | `1.59.0` |
| [github.com/redis/go-redis/v9](https://github.com/redis/go-redis) | `9.7.3` | `9.14.1` |
| [google.golang.org/grpc](https://github.com/grpc/grpc-go) | `1.83.1` | `1.84.0` |
| [github.com/wneessen/go-mail](https://github.com/wneessen/go-mail) | `0.7.2` | `0.8.1` |
| [github.com/nats-io/nats.go](https://github.com/nats-io/nats.go) | `1.53.1` | `1.54.0` |



Updates `github.com/modelcontextprotocol/go-sdk` from 1.6.1 to 1.8.0
- [Release notes](https://github.com/modelcontextprotocol/go-sdk/releases)
- [Commits](modelcontextprotocol/go-sdk@v1.6.1...v1.8.0)

Updates `modernc.org/sqlite` from 1.46.1 to 1.59.0
- [Changelog](https://gitlab.com/cznic/sqlite/blob/master/CHANGELOG.md)
- [Commits](https://gitlab.com/cznic/sqlite/compare/v1.46.1...v1.59.0)

Updates `github.com/redis/go-redis/v9` from 9.7.3 to 9.14.1
- [Release notes](https://github.com/redis/go-redis/releases)
- [Changelog](https://github.com/redis/go-redis/blob/v9.14.1/RELEASE-NOTES.md)
- [Commits](redis/go-redis@v9.7.3...v9.14.1)

Updates `google.golang.org/grpc` from 1.83.1 to 1.84.0
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](grpc/grpc-go@v1.83.1...v1.84.0)

Updates `github.com/wneessen/go-mail` from 0.7.2 to 0.8.1
- [Release notes](https://github.com/wneessen/go-mail/releases)
- [Commits](wneessen/go-mail@v0.7.2...v0.8.1)

Updates `github.com/nats-io/nats.go` from 1.53.1 to 1.54.0
- [Release notes](https://github.com/nats-io/nats.go/releases)
- [Commits](nats-io/nats.go@v1.53.1...v1.54.0)

---
updated-dependencies:
- dependency-name: github.com/modelcontextprotocol/go-sdk
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
- dependency-name: modernc.org/sqlite
  dependency-version: 1.59.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
- dependency-name: github.com/redis/go-redis/v9
  dependency-version: 9.14.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
- dependency-name: google.golang.org/grpc
  dependency-version: 1.84.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
- dependency-name: github.com/wneessen/go-mail
  dependency-version: 0.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
- dependency-name: github.com/nats-io/nats.go
  dependency-version: 1.54.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-minor-and-patch
...

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 Sep 26, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 3, 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 Oct 3, 2026
@dependabot
dependabot Bot deleted the dependabot/go_modules/go-minor-and-patch-1ceea1704b branch October 3, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants