Skip to content

Tidy the dependency tree #187

@lexfrei

Description

@lexfrei

The module tree has accumulated indirect-dep churn from upstream renames and version drift. Worth a coordinated sweep before the next major bump (helm v4 surfaced by the renovate custom manager, the Talos machinery upgrades, the kubernetes/staging packages, etc.) so that PR diffs from automation stay reviewable.

Scope:

  • Run go mod tidy and review the result — any unexpected additions or removals should be either retained with a one-line comment in go.mod or pruned.
  • Audit indirect deps that are present without a direct importer (often left behind by removed direct deps).
  • Identify deprecated packages with successors (e.g. anything still pulling in io/ioutil shims, deprecated golang.org/x/* paths) and migrate.
  • Confirm every replace directive in go.mod is still load-bearing; drop the stale ones.
  • Verify the build matrix in .github/workflows/pr.yml still passes after the cleanup on both Linux and Windows targets.

Goal is a tree where Renovate PRs can be merged with minimal cognitive load.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/releaseIssues or PRs related to release tooling (distribution, packaging)kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debtpriority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to completetriage/acceptedIndicates an issue is ready to be actively worked on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions