Skip to content

chore(deps): bump the go-dependencies group with 4 updates - #396

Merged
mxssl merged 2 commits into
mainfrom
dependabot/go_modules/go-dependencies-fe1aa43c6d
Oct 4, 2026
Merged

mxssl merged 2 commits into
mainfrom
dependabot/go_modules/go-dependencies-fe1aa43c6d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-dependencies group with 4 updates: github.com/ethereum/go-ethereum, github.com/klauspost/compress, github.com/labstack/echo/v4 and google.golang.org/genproto/googleapis/rpc.

Updates github.com/ethereum/go-ethereum from 1.17.5 to 1.17.6

Release notes

Sourced from github.com/ethereum/go-ethereum's releases.

Inorganic Lubricant (v1.17.6)

This is a maintenance release with a number of performance improvements to block processing and initial sync, and is recommended for all users.

A few things worth highlighting:

  • The Amsterdam hardfork is scheduled on the Sepolia testnet at timestamp 1791294816 (Oct 6, 2026, 13:53:36 UTC). Sepolia node operators must upgrade before that time.
  • The Holesky testnet has been removed, as the network reached end-of-life.
  • Go 1.24 is no longer supported. Release binaries and Docker images are now built with Go 1.27.

Fork Implementation

  • Schedule the Amsterdam fork on Sepolia (#35734)
  • Remove the EIP-7610 implementation (#35581)
  • Update EIP-2780 and EIP-8038 gas parameters (#35454, #35497)
  • Update EIP-7997 deterministic factory contract (#35458)
  • Update EIP-8037, repaying the outstanding gas debt first after absorbing a child frame (#35633)
  • Implement parallel block execution driven by the block-level access list (#35264, #35441, #35443, #35459, #35461, #35465, #35575, #35693)
  • Rename "regular gas" to "execution gas" to match EIP-8037 (#35457, #35486)

Core

  • Remove the Holesky testnet (#35591)
  • Optimize JSON decoding of large requests such as engine_newPayload (#35518)
  • Process the receipts for bloom construction and root calculation alongside execution (#35738)
  • Introduce a precompile result cache shared between prefetcher, block processing and miner (#35388, #35473, #35526, #35578, #35753)
  • Parallelize chain data and state writes in the post-execution commit (#35595)
  • Do not seal a block if a database error occurred (#35427)
  • Fix a panic in the log indexer when a reorg shortens the chain onto the rendered block (#35619)
  • Honor ExecuteConfig.EnableTracer for the EVM-level tracing hooks (#35512)
  • Add a metered LRU cache variant (#33719)
  • Retain block-level access lists alongside bad blocks (#35423)
  • Unset the block-level access list at the end of each transaction (#35498)
  • Fix the blob cache initialization (#35509)
  • Fix head truncation below a diverged tail group (#35551)
  • Improve the blob fetcher with a few defensive operations (#35572)
  • Fix deadlock when re-requesting partial receipts in eth/70 (#35537)
  • Reject empty partial receipt responses in eth/70 (#35593)
  • Cap the total size of blocked blob transactions in the sparse blobpool (#35367)
  • Fix the Cells/GetCells RLP encoding in eth/72 (#35428)
  • Cache recovered blobs in the blobpool to speed up serving pre-eth/72 peers (#35543)
  • Add fork validation for transaction types in the state transition (#35588)
  • Avoid announcing sparse blob txs to legacy peers (#35589)
  • Add eth/71 (EIP-8159) tests (#35389)
  • Fix gas tracer hooks and gas measurement (#35646)
  • The eth/72 blob buffer is capped at 128 MiB total and 16 MiB per peer (#35766)

Sync

... (truncated)

Commits
  • 3d84c6b version: release 1.17.6 (#35770)
  • bb81e22 cmd/geth, core, eth: add flag to disable precompile cache (#35753)
  • c6e3a0d core/txpool/blobpool: bound what the blob buffer holds (#35766)
  • 5b5c9d0 core, core/types: hash the receipts alongside execution (#35738)
  • 2aaf1a1 ethdb/memorydb: don't treat batch delete of the empty key as a range delete (...
  • c1c2f8d go.mod: update otel to 1.46.0 (#35754)
  • 23408c2 core/state: fix EIP number in selfdestruct comment (#35759)
  • 89def4a core, params: schedule amsterdam fork on sepolia (#35734)
  • a5b90d2 core, eth, miner, cmd/evm: ensure the parallel state processor records otel s...
  • 19bdbb0 eth/protocols/snap: port optimizations into snap v2 (#35705)
  • Additional commits viewable in compare view

Updates github.com/klauspost/compress from 1.20.0 to 1.20.1

Release notes

Sourced from github.com/klauspost/compress's releases.

v1.20.1

What's Changed

New Contributors

Full Changelog: klauspost/compress@v1.20.0...v1.20.1

Commits
  • 5d880f2 tests: Pre-release cleanups (#1231)
  • 5ed8a01 Report unexpected EOF for truncated Huffman extra bits (#1229)
  • 0bed724 flate: avoid FMA in EstimatedBits for portable rounding (#1224)
  • 147b531 zstd: apply reset options to reused frame decoders (#1226)
  • 58dac78 gzhttp: only decompress a request when gzip is the outermost coding (#1223)
  • 9b00a55 gzhttp: preserve caller request headers in Transport (#1225)
  • de8f55d ossfuzz: include zstd seqdec path tests (#1222)
  • a1c49c6 flate: precompute literal costs for findMatch (#1217)
  • ebd8190 flate: avoid the hand-rolled sorts when generating Huffman codes (#1214)
  • 4dc0d32 flate: use separate tables in histogramSplit (#1215)
  • Additional commits viewable in compare view

Updates github.com/labstack/echo/v4 from 4.15.4 to 4.16.0

Release notes

Sourced from github.com/labstack/echo/v4's releases.

v4.16.0

Security

This release fixes several security issues. Upgrading is recommended. Some fixes change behavior; read "Behavior changes to check before upgrading" below.

  • Request scheme: Context.Scheme() now uses the X-Forwarded-Proto, X-Forwarded-Protocol, X-Forwarded-Ssl and X-Url-Scheme headers only when the request comes directly from a loopback, link-local or private network address or a unix socket. Before this, any client could send X-Forwarded-Proto: https over plain HTTP and skip HTTPSRedirect. When X-Forwarded-Proto is present, only it is used (its last value), and the scheme is returned in lowercase. the new Echo#SchemeExtractor field selects the strategy: ExtractSchemeFromHeaders(...TrustOption) (default), ExtractSchemeDirect() or LegacySchemeExtractor(). The Secure middleware now sets HSTS based on Context.Scheme(). The Proxy middleware always sets X-Forwarded-Proto from Context.Scheme() and removes X-Forwarded-Ssl, X-Forwarded-Protocol and X-Url-Scheme before forwarding. GHSA-2ffq-g2xg-c22p
  • JSONP: Context.JSONP and Context.JSONPBlob accept only a callback that is empty, a JavaScript identifier or a dot-separated path of identifiers (ASCII letters, digits, _ and $). Any other callback returns a 400 Bad Request error that wraps the new ErrInvalidJSONPCallback, and nothing is written. JSONP responses now carry X-Content-Type-Options: nosniff. JSONP lets any website read the response with the user's cookies, so do not use it for data that needs authentication. GHSA-h9g5-28mm-hx3g
  • MethodOverride: a POST can no longer be overridden to GET, HEAD, OPTIONS, TRACE or CONNECT. Before this, with the MethodFromForm or MethodFromQuery getter and MethodOverride registered with Use before the CSRF middleware, _method=GET skipped the CSRF check. Register MethodOverride with Echo#Pre. GHSA-r7w9-592q-9vg4
  • Redirects: the trailing slash middlewares and the static directory redirect percent-encode control characters in the redirect path. Before this, /%09/evil.example/ redirected browsers to evil.example. GHSA-v753-g4cw-jm48
  • Static files: with the default settings, the Static middleware resolves files from the same form of the path that the router matched, so /admin%2Fsecret.txt or /%61dmin/secret.txt can no longer reach a file under a guarded /admin/* route. GHSA-375p-5qhx-8wq4 The Static middleware and StaticDirectoryHandler (used by Echo.Static, Echo.StaticFS, Group.Static and Group.StaticFS) no longer serve paths with a ., .. or empty segment, such as /assets/../admin/secret.txt, also after path unescaping. GHSA-3pmx-cf9f-34xr
  • Dependencies: update golang.org/x/text to v0.40.0 (GO-2026-5970).

Client IP address (no code change in v4)

Without Echo#IPExtractor, Context.RealIP() in v4 trusts the X-Forwarded-For and X-Real-IP headers from any client, so the rate limiter can be bypassed and the Proxy middleware forwards a spoofed X-Real-IP (GHSA-246p-cpwv-v3jq, GHSA-99jh-6h7p-pp36). Changing this default in v4 would put all clients behind a proxy into one rate-limit bucket, so v4 keeps it. Set an extractor that matches your deployment:

e.IPExtractor = echo.ExtractIPDirect()        // no proxy in front of the app
e.IPExtractor = echo.ExtractIPFromXFFHeader() // behind proxies in private networks that set X-Forwarded-For
// behind a proxy with public addresses (e.g. a CDN), also trust its ranges:
// e.IPExtractor = echo.ExtractIPFromXFFHeader(echo.TrustIPRange(cdnRange))

v5 uses the direct peer address by default since v5.1.0.

Behavior changes to check before upgrading

  • Proxies or load balancers with public IP addresses. If a proxy connects to your app from a public (or 100.64.0.0/10) address, its X-Forwarded-Proto is now ignored: HTTPSRedirect redirects in a loop and the Secure middleware stops sending HSTS. This affects, for example, Cloudflare, CloudFront and Azure Front Door connecting to a public origin, the GCP external HTTP(S) load balancer including GKE Ingress (35.191.0.0/16, 130.211.0.0/22), and networks that use 100.64.0.0/10 (such as Alibaba Cloud SLB or EKS custom networking). Trust the proxy's address ranges:
    _, gclb1, _ := net.ParseCIDR("35.191.0.0/16")
    _, gclb2, _ := net.ParseCIDR("130.211.0.0/22")
    e.SchemeExtractor = echo.ExtractSchemeFromHeaders(echo.TrustIPRange(gclb1), echo.TrustIPRange(gclb2))
    Proxies on the same host, in a private network (AWS ALB, in-cluster ingress controllers such as ingress-nginx or Traefik, most PaaS routers) or on a unix socket keep working without changes. echo.LegacySchemeExtractor() restores the old behavior but is not safe unless every request passes through a proxy that sets these headers. Serverless adapters or middleware that set RemoteAddr to the client's address also make X-Forwarded-Proto ignored (or, if they take it from a header, spoofable).
  • Trusted proxies must set X-Forwarded-Proto. A proxy on a trusted address that passes the client's X-Forwarded-Proto through (for example nginx without proxy_set_header X-Forwarded-Proto $scheme;) still lets the client choose the scheme. An invalid X-Forwarded-Proto value now results in http instead of falling back to the other scheme headers.
  • Your own tests. httptest.NewRequest sets RemoteAddr to 192.0.2.1:1234, which is not trusted, so tests that set X-Forwarded-Proto now see http. Set req.RemoteAddr = "10.0.0.1:1234" or use e.SchemeExtractor = echo.LegacySchemeExtractor() in such tests.
  • Proxy middleware headers. X-Forwarded-Ssl, X-Forwarded-Protocol and X-Url-Scheme are no longer forwarded to the upstream; X-Forwarded-Proto carries the scheme.
  • MethodOverride. Overriding a POST to GET (for example with X-HTTP-Method-Override: GET to send a long query in a POST body) is no longer done; such requests keep the POST method.
  • Static files. Paths with a double slash or dot segment (for example /assets//app.js) now return 404; in HTML5 mode the index is still served. The Static middleware no longer finds file names that the client sends with non-default escaping (for example %2C, %40 or lowercase hex like %c3%a9) unless StaticConfig.EnablePathUnescaping is set; Echo.Static has behaved this way since v4.15.4. With StaticConfig.EnablePathUnescaping or Echo#EnablePathUnescapingStaticFiles, encoded dots (%2e%2e) no longer traverse directories, but encoded slashes are still decoded, so do not combine these options with route-based access control.
  • JSONP. Context.JSONP returns an error for callbacks that are not JavaScript identifiers.

Documentation

  • Static middleware: when registered with Echo#Use it runs before route and group middleware, so route guards do not protect the files it serves.
Changelog

Sourced from github.com/labstack/echo/v4's changelog.

v4.16.0 - 2026-09-27

Security

This release fixes several security issues. Upgrading is recommended. Some fixes change behavior; read "Behavior changes to check before upgrading" below.

  • Request scheme: Context.Scheme() now uses the X-Forwarded-Proto, X-Forwarded-Protocol, X-Forwarded-Ssl and X-Url-Scheme headers only when the request comes directly from a loopback, link-local or private network address or a unix socket. Before this, any client could send X-Forwarded-Proto: https over plain HTTP and skip HTTPSRedirect. When X-Forwarded-Proto is present, only it is used (its last value), and the scheme is returned in lowercase. the new Echo#SchemeExtractor field selects the strategy: ExtractSchemeFromHeaders(...TrustOption) (default), ExtractSchemeDirect() or LegacySchemeExtractor(). The Secure middleware now sets HSTS based on Context.Scheme(). The Proxy middleware always sets X-Forwarded-Proto from Context.Scheme() and removes X-Forwarded-Ssl, X-Forwarded-Protocol and X-Url-Scheme before forwarding. GHSA-2ffq-g2xg-c22p
  • JSONP: Context.JSONP and Context.JSONPBlob accept only a callback that is empty, a JavaScript identifier or a dot-separated path of identifiers (ASCII letters, digits, _ and $). Any other callback returns a 400 Bad Request error that wraps the new ErrInvalidJSONPCallback, and nothing is written. JSONP responses now carry X-Content-Type-Options: nosniff. JSONP lets any website read the response with the user's cookies, so do not use it for data that needs authentication. GHSA-h9g5-28mm-hx3g
  • MethodOverride: a POST can no longer be overridden to GET, HEAD, OPTIONS, TRACE or CONNECT. Before this, with the MethodFromForm or MethodFromQuery getter and MethodOverride registered with Use before the CSRF middleware, _method=GET skipped the CSRF check. Register MethodOverride with Echo#Pre. GHSA-r7w9-592q-9vg4
  • Redirects: the trailing slash middlewares and the static directory redirect percent-encode control characters in the redirect path. Before this, /%09/evil.example/ redirected browsers to evil.example. GHSA-v753-g4cw-jm48
  • Static files: with the default settings, the Static middleware resolves files from the same form of the path that the router matched, so /admin%2Fsecret.txt or /%61dmin/secret.txt can no longer reach a file under a guarded /admin/* route. GHSA-375p-5qhx-8wq4 The Static middleware and StaticDirectoryHandler (used by Echo.Static, Echo.StaticFS, Group.Static and Group.StaticFS) no longer serve paths with a ., .. or empty segment, such as /assets/../admin/secret.txt, also after path unescaping. GHSA-3pmx-cf9f-34xr
  • Dependencies: update golang.org/x/text to v0.40.0 (GO-2026-5970).

Client IP address (no code change in v4)

Without Echo#IPExtractor, Context.RealIP() in v4 trusts the X-Forwarded-For and X-Real-IP headers from any client, so the rate limiter can be bypassed and the Proxy middleware forwards a spoofed X-Real-IP (GHSA-246p-cpwv-v3jq, GHSA-99jh-6h7p-pp36). Changing this default in v4 would put all clients behind a proxy into one rate-limit bucket, so v4 keeps it. Set an extractor that matches your deployment:

e.IPExtractor = echo.ExtractIPDirect()        // no proxy in front of the app
e.IPExtractor = echo.ExtractIPFromXFFHeader() // behind proxies in private networks that set X-Forwarded-For
// behind a proxy with public addresses (e.g. a CDN), also trust its ranges:
// e.IPExtractor = echo.ExtractIPFromXFFHeader(echo.TrustIPRange(cdnRange))

v5 uses the direct peer address by default since v5.1.0.

Behavior changes to check before upgrading

  • Proxies or load balancers with public IP addresses. If a proxy connects to your app from a public (or 100.64.0.0/10) address, its X-Forwarded-Proto is now ignored: HTTPSRedirect redirects in a loop and the Secure middleware stops sending HSTS. This affects, for example, Cloudflare, CloudFront and Azure Front Door connecting to a public origin, the GCP external HTTP(S) load balancer including GKE Ingress (35.191.0.0/16, 130.211.0.0/22), and networks that use 100.64.0.0/10 (such as Alibaba Cloud SLB or EKS custom networking). Trust the proxy's address ranges:
    _, gclb1, _ := net.ParseCIDR("35.191.0.0/16")
    _, gclb2, _ := net.ParseCIDR("130.211.0.0/22")
    e.SchemeExtractor = echo.ExtractSchemeFromHeaders(echo.TrustIPRange(gclb1), echo.TrustIPRange(gclb2))
    Proxies on the same host, in a private network (AWS ALB, in-cluster ingress controllers such as ingress-nginx or Traefik, most PaaS routers) or on a unix socket keep working without changes. echo.LegacySchemeExtractor() restores the old behavior but is not safe unless every request passes through a proxy that sets these headers. Serverless adapters or middleware that set RemoteAddr to the client's address also make X-Forwarded-Proto ignored (or, if they take it from a header, spoofable).
  • Trusted proxies must set X-Forwarded-Proto. A proxy on a trusted address that passes the client's X-Forwarded-Proto through (for example nginx without proxy_set_header X-Forwarded-Proto $scheme;) still lets the client choose the scheme. An invalid X-Forwarded-Proto value now results in http instead of falling back to the other scheme headers.
  • Your own tests. httptest.NewRequest sets RemoteAddr to 192.0.2.1:1234, which is not trusted, so tests that set X-Forwarded-Proto now see http. Set req.RemoteAddr = "10.0.0.1:1234" or use e.SchemeExtractor = echo.LegacySchemeExtractor() in such tests.
  • Proxy middleware headers. X-Forwarded-Ssl, X-Forwarded-Protocol and X-Url-Scheme are no longer forwarded to the upstream; X-Forwarded-Proto carries the scheme.
  • MethodOverride. Overriding a POST to GET (for example with X-HTTP-Method-Override: GET to send a long query in a POST body) is no longer done; such requests keep the POST method.
  • Static files. Paths with a double slash or dot segment (for example /assets//app.js) now return 404; in HTML5 mode the index is still served. The Static middleware no longer finds file names that the client sends with non-default escaping (for example %2C, %40 or lowercase hex like %c3%a9) unless StaticConfig.EnablePathUnescaping is set; Echo.Static has behaved this way since v4.15.4. With StaticConfig.EnablePathUnescaping or Echo#EnablePathUnescapingStaticFiles, encoded dots (%2e%2e) no longer traverse directories, but encoded slashes are still decoded, so do not combine these options with route-based access control.
  • JSONP. Context.JSONP returns an error for callbacks that are not JavaScript identifiers.

Documentation

  • Static middleware: when registered with Echo#Use it runs before route and group middleware, so route guards do not protect the files it serves.
Commits
  • e75c6c6 Merge pull request #3120 from labstack/chore/v4-bump-x-text
  • 7a49ed2 chore(deps): update golang.org/x/text to v0.40.0 (GO-2026-5970)
  • b838391 Merge commit from fork
  • 4f2f975 Fix body limit middleware state contamination with limitedReader pre-check
  • See full diff in compare view

Updates google.golang.org/genproto/googleapis/rpc from 0.0.0-20260706201446-f0a921348800 to 0.0.0-20260819154853-08b0e4226688

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the go-dependencies group with 4 updates: [github.com/ethereum/go-ethereum](https://github.com/ethereum/go-ethereum), [github.com/klauspost/compress](https://github.com/klauspost/compress), [github.com/labstack/echo/v4](https://github.com/labstack/echo) and [google.golang.org/genproto/googleapis/rpc](https://github.com/googleapis/go-genproto).


Updates `github.com/ethereum/go-ethereum` from 1.17.5 to 1.17.6
- [Release notes](https://github.com/ethereum/go-ethereum/releases)
- [Commits](ethereum/go-ethereum@v1.17.5...v1.17.6)

Updates `github.com/klauspost/compress` from 1.20.0 to 1.20.1
- [Release notes](https://github.com/klauspost/compress/releases)
- [Commits](klauspost/compress@v1.20.0...v1.20.1)

Updates `github.com/labstack/echo/v4` from 4.15.4 to 4.16.0
- [Release notes](https://github.com/labstack/echo/releases)
- [Changelog](https://github.com/labstack/echo/blob/v4.16.0/CHANGELOG.md)
- [Commits](labstack/echo@v4.15.4...v4.16.0)

Updates `google.golang.org/genproto/googleapis/rpc` from 0.0.0-20260706201446-f0a921348800 to 0.0.0-20260819154853-08b0e4226688
- [Commits](https://github.com/googleapis/go-genproto/commits)

---
updated-dependencies:
- dependency-name: github.com/ethereum/go-ethereum
  dependency-version: 1.17.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
- dependency-name: github.com/klauspost/compress
  dependency-version: 1.20.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
- dependency-name: github.com/labstack/echo/v4
  dependency-version: 4.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: google.golang.org/genproto/googleapis/rpc
  dependency-version: 0.0.0-20260819154853-08b0e4226688
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
...

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 Oct 1, 2026

@mxssl mxssl left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Only go.mod and go.sum change here, and the bumps are safe.

Verified locally on the PR head:

  • go mod verify and go mod tidy -diff are clean
  • go build ./..., go vet ./... and go test ./... pass (after make generate-networks)
  • e2e packages compile (go vet -tags=e2e ./test/e2e/...)

Notes:

  • e2e check failure is not caused by this PR. Dependabot-triggered runs don't get repo Actions secrets, so the job exits early with NODECORE_E2E_DRPC_KEY secret is required. Adding the secret under Dependabot secrets would let these PRs run e2e.
  • echo v4.16.0 is a security release that changes some behavior: Context.Scheme() now trusts X-Forwarded-* headers only from private or loopback peers, and JSONP, MethodOverride, Static and TrailingSlash are stricter. We don't use any of these (Scheme(), JSONP, MethodOverride, HTTPSRedirect, Secure, Proxy, Static*, RealIP, *TrailingSlash), so none of it affects us.
  • klauspost/compress v1.20.1 brings bug fixes and speedups for zstd and flate. Our internal/compression and stats gzip tests pass.
  • go-ethereum 1.17.6, genproto and otel 1.46 (indirect) are maintenance bumps.

@mxssl
mxssl merged commit 90e993c into main Oct 4, 2026
5 checks passed
@mxssl
mxssl deleted the dependabot/go_modules/go-dependencies-fe1aa43c6d branch October 4, 2026 20:57
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