chore(deps): remove unused module requirements - #13
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
rldyourmnd
deleted the
chore/remove-unused-module-dependencies-20260907
branch
September 7, 2026 16:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The module graph retained OpenPGP, YAML, x/sys, x/crypto and circl although no source or test imports them. Remove those unused requirements and checksums with
go mod tidy, keeping all used schema/test/tool dependencies at their existing versions. Public APIs and executable behavior are unchanged.Validation on Go 1.26.7:
go test -race ./...,go vet ./..., staticcheck v0.7.0, CLI build, the complete declared bounded fuzz contract, and cold compilation for linux/darwin on amd64/arm64 all passed. A secondgo mod tidy -diffis empty. Exact stable 0.8.0 bundle projection check passed. Source-mode govulncheck of the current CLI found no vulnerabilities before this cleanup; this is graph maintenance, not a claimed vulnerability fix or a new release.