Skip to content

Conversation

@cbandy
Copy link

@cbandy cbandy commented Aug 28, 2025

Updating these two direct dependencies reduces the number of indirect dependencies to almost zero. The gopkg.in/yaml.v2 module has moved to go.yaml.in/yaml/v2 and is now maintained by the YAML organization on GitHub.

Fixes: #154
See: https://www.github.com/pelletier/go-toml/issues/872
See: https://www.github.com/yaml/go-yaml/discussions/11

Updating these two direct dependencies reduces the number of indirect
dependencies to almost zero. The "gopkg.in/yaml.v2" module has moved
to "go.yaml.in/yaml/v2" and is now maintained by the YAML organization
on GitHub.

See: https://www.github.com/pelletier/go-toml/issues/872
See: https://www.github.com/yaml/go-yaml/discussions/11
@cbandy
Copy link
Author

cbandy commented Aug 28, 2025

$ (main) go mod graph | wc -l
23
$ (fewer-deps) go mod graph | wc -l
6

@peterbourgon
Copy link
Owner

peterbourgon commented Aug 28, 2025

I'm happy to dig into this but just to be clear "the number of indirect dependencies" is not a number that needs to be optimized for 😇 The ff module and its deps is always imported by something else, those importers will specify transitive dep versions as they require, and it is those end-user go.mods which dictate the ultimate compilation graph, not anything in ff itself.

@cbandy
Copy link
Author

cbandy commented Aug 28, 2025

True! I find things like this help with unsophisticated scanners in my day job: licenses, vulnerabilities, and such.

Certainly no urgency from me on this. 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dependency gopkg.in/yaml.v2 is now unmaintained

2 participants