Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 14, 2024

This PR contains the following updates:

Package Change Age Confidence Type Update
github.com/go-logr/logr v1.4.2 -> v1.4.3 age confidence require patch
github.com/kubescape/kubevuln v0.3.33 -> v0.3.85 age confidence require patch
github.com/kubescape/storage v0.0.111 -> v0.0.210 age confidence require patch
github.com/onsi/ginkgo/v2 v2.20.2 -> v2.25.2 age confidence require minor
github.com/onsi/gomega v1.34.2 -> v1.38.2 age confidence require minor
github.com/validator-labs/validator v0.1.0 -> v0.1.16 age confidence require patch
golang 1.23 -> 1.25 age confidence stage minor
k8s.io/api v0.31.0 -> v0.34.0 age confidence require minor
k8s.io/apimachinery v0.31.0 -> v0.34.0 age confidence require minor
k8s.io/client-go v0.31.0 -> v0.34.0 age confidence require minor
sigs.k8s.io/cluster-api v1.8.2 -> v1.11.0 age confidence require minor
sigs.k8s.io/controller-runtime v0.19.0 -> v0.22.0 age confidence require minor

Release Notes

go-logr/logr (github.com/go-logr/logr)

v1.4.3

Compare Source

Minor release.

What's Changed

New Contributors

Full Changelog: go-logr/logr@v1.4.2...v1.4.3

kubescape/kubevuln (github.com/kubescape/kubevuln)

v0.3.85

Compare Source

Bumps github.com/hashicorp/go-getter from 1.7.6 to 1.7.9.

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.9

What's Changed

New Contributors

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.8...v1.7.9

v1.7.8

What's Changed

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.7...v1.7.8

v1.7.7

What's Changed

New Contributors

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.6...v1.7.7

Commits
  • e702211 Merge pull request #​532 from hashicorp/dependabot/github_actions/actions-8948...
  • df0a14f [chore] : Bump the actions group with 8 updates
  • 87541b2 fix: go-getter subdir paths (#​540)
  • 3713030 [Compliance] - PR Template Changes Required
  • af2dd3c Merge pull request #​529 from hashicorp/dependabot-intge
  • bf52629 updating dependabot.yml
  • 1f63e10 changelog added, updated dependabot.yaml
  • 45af459 fix additional lint errors and increase linter scope
  • c8c6aba fix errcheck lint errors and run it as part of pr checks
  • 9b76f98 copywrite header added
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

v0.3.84

Compare Source

Bumps github.com/docker/docker from 27.4.0+incompatible to 28.0.0+incompatible.

Release notes

Sourced from github.com/docker/docker's releases.

v28.0.0

28.0.0

For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:

New

  • Add ability to mount an image inside a container via --mount type=image. moby/moby#48798
    • You can also specify --mount type=image,image-subpath=[subpath],... option to mount a specific path from the image. docker/cli#5755
  • docker images --tree now shows metadata badges. docker/cli#5744
  • docker load, docker save, and docker history now support a --platform flag allowing you to choose a specific platform for single-platform operations on multi-platform images. docker/cli#5331
  • Add OOMScoreAdj to docker service create and docker stack. docker/cli#5145
  • docker buildx prune now supports reserved-space, max-used-space, min-free-space and keep-bytes filters. moby/moby#48720
  • Windows: Add support for running containerd as a child process of the daemon, instead of using a system-installed containerd. moby/moby#47955

Networking

  • The docker-proxy binary has been updated, older versions will not work with the updated dockerd. moby/moby#48132
    • Close a window in which the userland proxy (docker-proxy) could accept TCP connections, that would then fail after iptables NAT rules were set up.
    • The executable rootlesskit-docker-proxy is no longer used, it has been removed from the build and distribution.
  • DNS nameservers read from the host's /etc/resolv.conf are now always accessed from the host's network namespace. moby/moby#48290
    • When the host's /etc/resolv.conf contains no nameservers and there are no --dns overrides, Google's DNS servers are no longer used, apart from by the default bridge network and in build containers.
  • Container interfaces in bridge and macvlan networks now use randomly generated MAC addresses. moby/moby#48808
    • Gratuitous ARP / Neighbour Advertisement messages will be sent when the interfaces are started so that, when IP addresses are reused, they're associated with the newly generated MAC address.
    • IPv6 addresses in the default bridge network are now IPAM-assigned, rather than being derived from the MAC address.
  • The deprecated OCI prestart hook is now only used by build containers. For other containers, network interfaces are added to the network namespace after task creation is complete, before the container task is started. moby/moby#47406
  • Add a new gw-priority option to docker run, docker container create, and docker network connect. This option will be used by the Engine to determine which network provides the default gateway for a container. On docker run, this option is only available through the extended --network syntax. docker/cli#5664
  • Add a new netlabel com.docker.network.endpoint.ifname to customize the interface name used when connecting a container to a network. It's supported by all built-in network drivers on Linux. moby/moby#49155
    • When a container is created with multiple networks specified, there's no guarantee on the order networks will be connected to the container. So, if a custom interface name uses the same prefix as the auto-generated names, for example eth, the container might fail to start.
    • The recommended practice is to use a different prefix, for example en0, or a numerical suffix high enough to never collide, for example eth100.
    • This label can be specified on docker network connect via the --driver-opt flag, for example docker network connect --driver-opt=com.docker.network.endpoint.ifname=foobar ….
    • Or via the long-form --network flag on docker run, for example docker run --network=name=bridge,driver-opt=com.docker.network.endpoint.ifname=foobar …
  • If a custom network driver reports capability GwAllocChecker then, before a network is created, it will get a GwAllocCheckerRequest with the network's options. The custom driver may then reply that no gateway IP address should be allocated. moby/moby#49372

Port publishing in bridge networks

  • dockerd now requires ipset support in the Linux kernel. moby/moby#48596
    • The iptables and ip6tables rules used to implement port publishing and network isolation have been extensively modified. This enables some of the following functional changes, and is a first step in refactoring to enable native nftables support in a future release. moby/moby#48815
    • If it becomes necessary to downgrade to an earlier version of the daemon, some manual cleanup of the new rules will be necessary. The simplest and surest approach is to reboot the host, or use iptables -F and ip6tables -F to flush all existing iptables rules from the filter table before starting the older version of the daemon. When that is not possible, run the following commands as root:
      • iptables -D FORWARD -m set --match-set docker-ext-bridges-v4 dst -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT; ip6tables -D FORWARD -m set --match-set docker-ext-bridges-v6 dst -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
      • iptables -D FORWARD -m set --match-set docker-ext-bridges-v4 dst -j DOCKER; ip6tables -D FORWARD -m set --match-set docker-ext-bridges-v6 dst -j DOCKER
      • If you were previously running with the iptables filter-FORWARD policy set to ACCEPT and need to restore access to unpublished ports, also delete per-bridge-network rules from the DOCKER chains. For example, iptables -D DOCKER ! -i docker0 -o docker0 -j DROP.
  • Fix a security issue that was allowing remote hosts to connect directly to a container on its published ports. moby/moby#49325
  • Fix a security issue that was allowing neighbor hosts to connect to ports mapped on a loopback address. moby/moby#49325

... (truncated)

Commits

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

v0.3.83

Compare Source

Overview

v0.3.82

Compare Source

Overview

v0.3.80

Compare Source

v0.3.78

Compare Source

v0.3.77

Compare Source

v0.3.76

Compare Source

Bumps github.com/open-policy-agent/opa from 0.68.0 to 1.4.0.

Release notes

Sourced from github.com/open-policy-agent/opa's releases.

v1.4.0

This release contains a security fix addressing CVE-2025-46569. It also includes a mix of new features, bugfixes, and dependency updates.

Security Fix: CVE-2025-46569 - OPA server Data API HTTP path injection of Rego (GHSA-6m8w-jc87-6cr7)

A vulnerability in the OPA server's Data API allows an attacker to craft the HTTP path in a way that injects Rego code into the query that is evaluated.
The evaluation result cannot be made to return any other data than what is generated by the requested path, but this path can be misdirected, and the injected Rego code can be crafted to make the query succeed or fail; opening up for oracle attacks or, given the right circumstances, erroneous policy decision results. Furthermore, the injected code can be crafted to be computationally expensive, resulting in a Denial Of Service (DoS) attack.

Users are only impacted if all of the following apply:

  • OPA is deployed as a standalone server (rather than being used as a Go library)
  • The OPA server is exposed outside of the local host in an untrusted environment.
  • The configured authorization policy does not do exact matching of the input.path attribute when deciding if the request should be allowed.

or, if all of the following apply:

  • OPA is deployed as a standalone server.
  • The service connecting to OPA allows 3rd parties to insert unsanitised text into the path of the HTTP request to OPA’s Data API.

Note: With no Authorization Policy configured for restricting API access (the default configuration), the RESTful Data API provides access for managing Rego policies; and the RESTful Query API facilitates advanced queries. Full access to these APIs provides both simpler, and broader access than what the security issue describes here can facilitate. As such, OPA servers exposed to a network are not considered affected by the attack described here if they are knowingly not restricting access through an Authorization Policy.

This issue affects all versions of OPA prior to 1.4.0.

See the Security Advisory for more details.

Reported by @​​GamrayW, @​​HyouKash, @​​AdrienIT, authored by @​​johanfylling

Runtime, Tooling, SDK

Topdown and Rego

Docs, Website, Ecosystem

... (truncated)

Changelog

Sourced from github.com/open-policy-agent/opa's changelog.

1.4.0

This release contains a security fix addressing CVE-2025-46569. It also includes a mix of new features, bugfixes, and dependency updates.

Security Fix: CVE-2025-46569 - OPA server Data API HTTP path injection of Rego (GHSA-6m8w-jc87-6cr7)

A vulnerability in the OPA server's Data API allows an attacker to craft the HTTP path in a way that injects Rego code into the query that is evaluated.
The evaluation result cannot be made to return any other data than what is generated by the requested path, but this path can be misdirected, and the injected Rego code can be crafted to make the query succeed or fail; opening up for oracle attacks or, given the right circumstances, erroneous policy decision results. Furthermore, the injected code can be crafted to be computationally expensive, resulting in a Denial Of Service (DoS) attack.

Users are only impacted if all of the following apply:

  • OPA is deployed as a standalone server (rather than being used as a Go library)
  • The OPA server is exposed outside of the local host in an untrusted environment.
  • The configured authorization policy does not do exact matching of the input.path attribute when deciding if the request should be allowed.

or, if all of the following apply:

  • OPA is deployed as a standalone server.
  • The service connecting to OPA allows 3rd parties to insert unsanitised text into the path of the HTTP request to OPA’s Data API.

Note: With no Authorization Policy configured for restricting API access (the default configuration), the RESTful Data API provides access for managing Rego policies; and the RESTful Query API facilitates advanced queries. Full access to these APIs provides both simpler, and broader access than what the security issue describes here can facilitate. As such, OPA servers exposed to a network are not considered affected by the attack described here if they are knowingly not restricting access through an Authorization Policy.

This issue affects all versions of OPA prior to 1.4.0.

See the Security Advisory for more details.

Reported by @​​GamrayW, @​​HyouKash, @​​AdrienIT, authored by @​​johanfylling

Runtime, Tooling, SDK

Topdown and Rego

Docs, Website, Ecosystem

... (truncated)

Commits

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

v0.3.75

Compare Source

Please see kubescape/kubescape#1834

v0.3.74

Compare Source

Bumps github.com/cilium/cilium from 1.16.8 to 1.16.9.

Release notes

Sourced from github.com/cilium/cilium's releases.

1.16.9

Summary of Changes

Minor Changes:

Bugfixes:

CI Changes:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner November 14, 2024 23:05
@renovate renovate bot requested a review from TylerGillson November 14, 2024 23:05
Copy link
Contributor Author

renovate bot commented Nov 14, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 71 additional dependencies were updated

Details:

Package Change
github.com/anchore/go-logger v0.0.0-20230725134548-c21dafa1ec5a -> v0.0.0-20241205183533-4fc29b5832e7
github.com/anchore/packageurl-go v0.1.1-0.20240312213626-055233e539b4 -> v0.1.1-0.20241018175412-5c22e6360c4f
github.com/anchore/stereoscope v0.0.3-0.20240423181235-8b297badafd5 -> v0.0.11
github.com/anchore/syft v1.3.0 -> v1.18.1
github.com/armosec/armoapi-go v0.0.416 -> v0.0.512
github.com/armosec/gojay v1.2.15 -> v1.2.17
github.com/armosec/utils-go v0.0.57 -> v0.0.58
github.com/armosec/utils-k8s-go v0.0.26 -> v0.0.30
github.com/bmatcuk/doublestar/v4 v4.6.1 -> v4.7.1
github.com/briandowns/spinner v1.23.0 -> v1.23.1
github.com/containerd/errdefs v0.1.0 -> v1.0.0
github.com/docker/cli v24.0.7+incompatible -> v27.4.0+incompatible
github.com/docker/docker v27.1.1+incompatible -> v27.4.0+incompatible
github.com/emicklei/go-restful/v3 v3.12.1 -> v3.12.2
github.com/evanphx/json-patch/v5 v5.9.0 -> v5.9.11
github.com/fatih/color v1.17.0 -> v1.18.0
github.com/fsnotify/fsnotify v1.7.0 -> v1.8.0
github.com/gabriel-vasile/mimetype v1.4.3 -> v1.4.7
github.com/github/go-spdx/v2 v2.2.0 -> v2.3.2
github.com/gobuffalo/flect v1.0.2 -> v1.0.3
github.com/google/cel-go v0.20.1 -> v0.22.0
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/google/go-containerregistry v0.20.1 -> v0.20.2
github.com/google/pprof v0.0.0-20240827171923-fa2c70bbbfe5 -> v0.0.0-20250403155104-27863c87afa6
github.com/grpc-ecosystem/grpc-gateway/v2 v2.20.0 -> v2.26.1
github.com/klauspost/compress v1.17.9 -> v1.17.11
github.com/kubescape/go-logger v0.0.22 -> v0.0.23
github.com/kubescape/k8s-interface v0.0.162 -> v0.0.191
github.com/pelletier/go-toml/v2 v2.2.2 -> v2.2.3
github.com/pierrec/lz4/v4 v4.1.15 -> v4.1.22
github.com/prometheus/client_golang v1.19.1 -> v1.20.5
github.com/prometheus/common v0.55.0 -> v0.61.0
github.com/sagikazarmark/locafero v0.4.0 -> v0.7.0
github.com/spf13/afero v1.11.0 -> v1.12.0
github.com/spf13/cast v1.6.0 -> v1.7.1
github.com/spf13/cobra v1.8.1 -> v1.9.1
github.com/spf13/pflag v1.0.5 -> v1.0.6
github.com/spf13/viper v1.19.0 -> v1.20.0
github.com/stoewer/go-strcase v1.2.0 -> v1.3.0
github.com/stripe/stripe-go/v74 v74.28.0 -> v74.30.0
github.com/sylabs/squashfs v0.6.1 -> v1.0.4
github.com/uptrace/opentelemetry-go-extra/otelutil v0.2.2 -> v0.3.2
github.com/uptrace/opentelemetry-go-extra/otelzap v0.2.2 -> v0.3.2
github.com/uptrace/uptrace-go v1.18.0 -> v1.30.1
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.53.0 -> v0.58.0
go.opentelemetry.io/contrib/instrumentation/runtime v0.44.0 -> v0.55.0
go.opentelemetry.io/otel v1.28.0 -> v1.35.0
go.opentelemetry.io/otel/exporters/stdout/stdouttrace v1.18.0 -> v1.30.0
go.opentelemetry.io/otel/metric v1.28.0 -> v1.35.0
go.opentelemetry.io/otel/sdk v1.28.0 -> v1.35.0
golang.org/x/crypto v0.26.0 -> v0.36.0
golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56 -> v0.0.0-20241217172543-b2144cdd0a67
golang.org/x/net v0.28.0 -> v0.37.0
golang.org/x/oauth2 v0.21.0 -> v0.28.0
golang.org/x/sync v0.8.0 -> v0.12.0
golang.org/x/sys v0.24.0 -> v0.32.0
golang.org/x/term v0.23.0 -> v0.30.0
golang.org/x/text v0.17.0 -> v0.23.0
golang.org/x/time v0.5.0 -> v0.8.0
golang.org/x/tools v0.24.0 -> v0.31.0
gomodules.xyz/jsonpatch/v2 v2.4.0 -> v2.5.0
google.golang.org/genproto/googleapis/api v0.0.0-20240528184218-531527333157 -> v0.0.0-20250218202821-56aae31c358a
google.golang.org/genproto/googleapis/rpc v0.0.0-20240701130421-f6361c86f094 -> v0.0.0-20250218202821-56aae31c358a
k8s.io/apiextensions-apiserver v0.31.0 -> v0.32.3
k8s.io/apiserver v0.31.0 -> v0.32.3
k8s.io/component-base v0.31.0 -> v0.32.3
k8s.io/kube-openapi v0.0.0-20240228011516-70dd3763d340 -> v0.0.0-20241105132330-32ad38e42d3f
k8s.io/utils v0.0.0-20240711033017-18e509b52bc8 -> v0.0.0-20241210054802-24370beab758
sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.30.3 -> v0.31.0
sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd -> v0.0.0-20241014173422-cfa47c3a1cc8
sigs.k8s.io/structured-merge-diff/v4 v4.4.1 -> v4.5.0

@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Nov 14, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 14, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 19, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 19, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 21, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 21, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 21, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 22, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Nov 22, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 88d5bb5 to edf0874 Compare July 16, 2025 11:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from cf29075 to 07e1f0b Compare July 28, 2025 18:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 8a020b5 to 0b83298 Compare August 5, 2025 13:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a7eb530 to 2fbcba7 Compare August 14, 2025 06:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from c85533c to dc8cfea Compare August 22, 2025 18:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 1ef4ef4 to 12cc0b9 Compare August 28, 2025 01:47
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 12cc0b9 to bb9a1f8 Compare August 28, 2025 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies go size:S This PR changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants