chore(deps): update all module dependencies #45
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/update-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Dependency-only release prep:
go get -u ./... && go mod tidy.Key movements:
munnerz/goautoneg, dropskr/textandclipperhouse/stringishfrom the graph)Direct deps already at latest (cobra, jsonschema, yaml.v3, bubbletea/bubbles/lipgloss) are unchanged.
Verified:
go build/vet/test ./.../gofmtclean, plusmake cudaandgo test -tags cuda -count=1 ./internal/backend/cuda/ ./internal/model/mistral/on the Blackwell box.Automated review by pr-reviewer v0.36.0 | Safety Check | Claude Sonnet 5 | tracking id
r-6051e5-706564This is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — Routine, verified dependency bump with no source changes; the go.sum entropy flag is a false positive since go.sum entries are always base64 hash data.
This is a routine dependency bump (go.mod/go.sum only), matching the PR description exactly: version bumps for prometheus client libs, x/sys, x/text, protobuf, and charmbracelet transitive deps, with corresponding additions/removals of transitive packages (goautoneg added, kr/text and clipperhouse/stringish dropped). No source code changes. The "high entropy" flag on go.sum is expected/benign — go.sum lines are base64-encoded hashes, which always look like high-entropy data; this is normal and not a sign of accidentally committed secrets or binaries. PR author states build/vet/test/gofmt all clean, plus CUDA-specific tests passed. No signs of malicious or accidental content.