Skip to content

build(deps): bump the gomod-minor group across 1 directory with 3 updates - #511

Merged
bomly-guy merged 1 commit into
mainfrom
dependabot/go_modules/gomod-minor-d48f4ee056
Oct 19, 2026
Merged

bomly-guy merged 1 commit into
mainfrom
dependabot/go_modules/gomod-minor-d48f4ee056

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the gomod-minor group with 3 updates in the / directory: github.com/mark3labs/mcp-go, golang.org/x/term and golang.org/x/tools.

Updates github.com/mark3labs/mcp-go from 1.1.1 to 1.3.0

Release notes

Sourced from github.com/mark3labs/mcp-go's releases.

Release v1.3.0

What's Changed

New Contributors

Full Changelog: mark3labs/mcp-go@v1.2.1...v1.3.0

Release v1.2.1

What's Changed

Full Changelog: mark3labs/mcp-go@v1.2.0...v1.2.1

... (truncated)

Commits
  • e1bd0ab Revert "chore: prepare v2.0.0 module migration"
  • ba63c02 chore: prepare v2.0.0 module migration
  • 3751c4a fix(mcp): retain typed task status fields and result envelopes (#1071)
  • 110d9f8 fix(client): allow failed listener callbacks to stop their stream (#1070)
  • 7cf0abd fix(mcp): return encodable errors for invalid structured results (#1069)
  • 05bdc1a fix(transport): include client session in in-process notifications (#1067)
  • 8e0e120 fix(server): invoke task lifecycle observers after unlocking (#1065)
  • dd4fea0 feat(server): limit the size of a tool result (#1048)
  • 14138d0 fix(transport): don't take SSE server requests as responses (#1085)
  • ef25288 fix(server): serialize stdio session requests with other writes (#1084)
  • Additional commits viewable in compare view

Updates golang.org/x/term from 0.46.0 to 0.47.0

Commits

Updates golang.org/x/tools from 0.50.0 to 0.52.0

Commits
  • 16517d9 go.mod: update golang.org/x dependencies
  • a39b773 gopls/internal/cache: fix shadowing bug
  • 2faede3 gopls/internal/test/marker: reorganize undeclared test files
  • dbca0bb go/ssa: support pointer-typed composite literals in all contexts
  • ec72d2b gopls/internal/cache: pass overlays to go mod commands
  • 2c54968 gopls/internal/golang: MoveDeclaration - fix imports for decls in multiple files
  • 1e27b6e internal/cursorutil: promote from gopls, plus other cleanups
  • 2babe1e gopls/internal/lsprpc: adjust dial retry logic
  • a3af45f internal/refactor/inline: reduce void calls in tail position
  • ac4a446 gopls/internal/filewatcher: disable TestStress/fsnotify on 386
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from bomly-guy as a code owner October 14, 2026 00:42
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Oct 14, 2026
@coderabbitai

coderabbitai Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Repository: bomly-dev/bomly-cli/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6423aae5-6ee3-4312-996a-a9adeee72366

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Bomly Diff Summary

Compared 5039e43eefd809cf5f8cf4104b8d4abfd508fc38 to e5118b8ba2d60e42085eb26c683c7d36773dd866.

Overview

Status Manifests Dependencies Findings Duration
✅ Pass +0 / ~1 / -0 0 added / 10 version changed / 0 detail changes / 0 removed 0 introduced / 0 persisted / 5 resolved 1m 35s

Dependency Changes

Summary: 0 added, 10 version changed, 0 detail changes, 0 removed.

Changed Dependencies

Change Package Version Direct? Scope Licenses
changed github.com/mark3labs/mcp-go v1.1.1 → v1.3.0 Yes runtime MIT
changed golang.org/x/crypto v0.57.0 → v0.58.0 No runtime BSD-3-Clause
changed golang.org/x/mod v0.41.0 → v0.42.0 No runtime BSD-3-Clause
changed golang.org/x/net v0.59.0 → v0.61.0 No runtime BSD-3-Clause
changed golang.org/x/sync v0.23.0 → v0.24.0 No runtime BSD-3-Clause
changed golang.org/x/sys v0.48.0 → v0.49.0 No runtime BSD-3-Clause
changed golang.org/x/telemetry v0.0.0-20260908163034-4bcc4b2ee518 → v0.0.0-20261009151841-97e8ea77aa2a No runtime BSD-3-Clause
changed golang.org/x/term v0.46.0 → v0.47.0 Yes runtime BSD-3-Clause
changed golang.org/x/text v0.42.0 → v0.43.0 No runtime BSD-3-Clause
changed golang.org/x/tools v0.50.0 → v0.52.0 Yes runtime BSD-3-Clause

Vulnerabilities

Summary: 0 introduced, 1 persisted, 5 resolved.

Persisted Vulnerabilities

Change Severity ID Package Fixed In Source Title
persisted UNKNOWN GO-2026-5932 golang.org/x/crypto@v0.58.0 - grype The golang.org/x/crypto/openpgp package is unsafe by design, has numerous known security issues, is not maintained, and should not be used. If you are required to interoperate with OpenPGP systems and need a maintained package, consider github.com/ProtonMail/go-crypto/openpgp which is a maintained fork that aims to be a drop-in replacement for this package.

Resolved Vulnerabilities

Change Severity ID Package Fixed In Source Title
resolved CRITICAL GO-2026-6612 golang.org/x/net@v0.59.0 0.60.0 grype The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
resolved HIGH GO-2026-6603 golang.org/x/net@v0.59.0 0.60.0 grype When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
resolved HIGH GO-2026-6610 golang.org/x/net@v0.59.0 0.60.0 grype Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
resolved HIGH GO-2026-6611 golang.org/x/net@v0.59.0 0.60.0 grype A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
resolved HIGH GO-2026-6617 golang.org/x/net@v0.59.0 0.60.0 grype HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

License Changes

✅ No license changes.

Project Posture

✅ No project posture changes (--matchers +scorecard was not selected).

Policy Findings

Summary: 0 introduced, 0 persisted, 5 resolved.

Resolved Findings

Status Category Severity ID Package Fixed In Title
✅ resolved vulnerability CRITICAL GO-2026-6612 golang.org/x/net@v0.59.0 0.60.0 The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
✅ resolved vulnerability HIGH GO-2026-6603 golang.org/x/net@v0.59.0 0.60.0 When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
✅ resolved vulnerability HIGH GO-2026-6610 golang.org/x/net@v0.59.0 0.60.0 Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
✅ resolved vulnerability HIGH GO-2026-6611 golang.org/x/net@v0.59.0 0.60.0 A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
✅ resolved vulnerability HIGH GO-2026-6617 golang.org/x/net@v0.59.0 0.60.0 HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

Legend: ✅ resolved · ❌ failing · ⚠️ warning

Remediation

ℹ️ No fix suggestions available for 1 vulnerable package.

Vulnerable package Status Recommended version Action Suggested action for Manifest Manager advice
golang.org/x/crypto@v0.58.0 Fix availability unknown - Manual review pkg:golang/github.com/bomly-dev/bomly-plugin-grype-matcher@v0.7.0 go.mod -

@dependabot
dependabot Bot force-pushed the dependabot/go_modules/gomod-minor-d48f4ee056 branch 2 times, most recently from 6846605 to 95b2747 Compare October 19, 2026 06:36
@bomly-guy

Copy link
Copy Markdown
Collaborator

@dependabot rebase

…ates

Bumps the gomod-minor group with 3 updates in the / directory: [github.com/mark3labs/mcp-go](https://github.com/mark3labs/mcp-go), [golang.org/x/term](https://github.com/golang/term) and [golang.org/x/tools](https://github.com/golang/tools).


Updates `github.com/mark3labs/mcp-go` from 1.1.1 to 1.3.0
- [Release notes](https://github.com/mark3labs/mcp-go/releases)
- [Commits](mark3labs/mcp-go@v1.1.1...v1.3.0)

Updates `golang.org/x/term` from 0.46.0 to 0.47.0
- [Commits](golang/term@v0.46.0...v0.47.0)

Updates `golang.org/x/tools` from 0.50.0 to 0.52.0
- [Release notes](https://github.com/golang/tools/releases)
- [Commits](golang/tools@v0.50.0...v0.52.0)

---
updated-dependencies:
- dependency-name: github.com/mark3labs/mcp-go
  dependency-version: 1.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: gomod-minor
- dependency-name: golang.org/x/term
  dependency-version: 0.47.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: gomod-minor
- dependency-name: golang.org/x/tools
  dependency-version: 0.52.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: gomod-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/go_modules/gomod-minor-d48f4ee056 branch from 95b2747 to e5118b8 Compare October 19, 2026 06:42
@bomly-guy
bomly-guy merged commit e7e540c into main Oct 19, 2026
14 checks passed
@bomly-guy
bomly-guy deleted the dependabot/go_modules/gomod-minor-d48f4ee056 branch October 19, 2026 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant