build(deps): bump github.com/replicatedhq/troubleshoot from 0.127.1 to 0.129.1#3753
Conversation
Bumps [github.com/replicatedhq/troubleshoot](https://github.com/replicatedhq/troubleshoot) from 0.127.1 to 0.129.1. - [Release notes](https://github.com/replicatedhq/troubleshoot/releases) - [Commits](replicatedhq/troubleshoot@v0.127.1...v0.129.1) --- updated-dependencies: - dependency-name: github.com/replicatedhq/troubleshoot dependency-version: 0.129.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7d0f12d. Configure here.
| k8s.io/metrics v0.35.4 // indirect | ||
| k8s.io/metrics v0.36.1 // indirect | ||
| k8s.io/mount-utils v0.35.4 // indirect | ||
| k8s.io/streaming v0.36.1 // indirect |
There was a problem hiding this comment.
Kubernetes streaming version skew
Medium Severity
Bumping github.com/replicatedhq/troubleshoot to v0.129.1 pulls in k8s.io/streaming v0.36.1, while go.mod still replaces other k8s.io/* modules to v0.35.4 for k0s alignment and does not pin k8s.io/streaming. The binary therefore mixes Kubernetes client minor versions on exec/streaming paths used by updated troubleshoot collectors.
Reviewed by Cursor Bugbot for commit 7d0f12d. Configure here.
| k8s.io/utils v0.0.0-20260319190234-28399d86e0b5 | ||
| oras.land/oras-go/v2 v2.6.0 | ||
| sigs.k8s.io/controller-runtime v0.23.3 | ||
| sigs.k8s.io/controller-runtime v0.24.1 |
There was a problem hiding this comment.
Controller-runtime k8s mismatch
Medium Severity
This change upgrades the direct sigs.k8s.io/controller-runtime requirement from v0.23.3 to v0.24.1 while replace directives still force all k8s.io/* staging modules (including client-go) to v0.35.4 for k0s. Controller-runtime v0.24 targets Kubernetes 1.36 client libraries, so the operator and other in-tree controller-runtime clients no longer match the pinned cluster client stack.
Reviewed by Cursor Bugbot for commit 7d0f12d. Configure here.
| github.com/replicatedhq/embedded-cluster/utils v0.0.0 | ||
| github.com/replicatedhq/kotskinds v0.0.0-20251024162531-2174a5b85a4d | ||
| github.com/replicatedhq/troubleshoot v0.127.1 | ||
| github.com/replicatedhq/troubleshoot v0.129.1 |
There was a problem hiding this comment.
Preflight binary version drift
Medium Severity
The PR bumps github.com/replicatedhq/troubleshoot in go.mod to v0.129.1 but does not update TROUBLESHOOT_VERSION in versions.mk, which still selects v0.128.1 release artifacts for bundled preflight and support-bundle binaries. Host preflight specs are built from the newer Go module while installs invoke an older CLI, so behavior can diverge or fail on newer spec fields.
Reviewed by Cursor Bugbot for commit 7d0f12d. Configure here.
|
Superseded by #3769. |
dependabot
Bot
deleted the
dependabot/go_modules/github.com/replicatedhq/troubleshoot-0.129.1
branch
Bumps github.com/replicatedhq/troubleshoot from 0.127.1 to 0.129.1.
Release notes
Sourced from github.com/replicatedhq/troubleshoot's releases.
Commits
baecd3cchore(deps): bump golang.org/x/net, x/crypto, containerd to patch CVEs (#2049...1cfa00echore(deps): bump the security group with 3 updates (#2048)9600c17chore(deps): bump github.com/containerd/containerd from 1.7.30 to 1.7.32 (#2046)61ef1e1fix: TLS support in MySQL connector (#2045)77e39bcchore(deps): bump helm.sh/helm/v3 from 3.20.2 to 3.21.0 in /examples/sdk/helm...edba8f1chore(deps): bump the security group with 14 updates (#2043)8941587Bump Go from 1.26.2 to 1.26.3 (#2040)1cd9b61feat: Add Clickhouse Support (#1967)ba33b74chore(deps): bump the security group with 5 updates (#2042)f6c5760chore(deps): bump github.com/distribution/distribution/v3 from 3.1.0 to 3.1.1...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)