dfda61bbbf
Makefile's target `verify-dep` current behavior is to use `go list` to check consistent dependency versions from direct dependencies. Ignoring indirect dependencies in a multi-module project could lead to version mismatches. If module A imports module B, module B's dependency will be an indirect dependency in module A. Which can potentially have a version mismatch. Therefore, use `go mod edit` with indirect dependencies, too. So it can work with all dependencies defined in go.mod. Fix displaying dependencies with mismatches, as the old code was searching with grep just for the prefix, which would show other dependencies that shared the same prefix. Signed-off-by: Ivan Valdes <ivan@vald.es> |
||
|---|---|---|
| .. | ||
| build_lib.sh | ||
| build_tools.sh | ||
| build-binary.sh | ||
| build-docker.sh | ||
| build-release.sh | ||
| build.sh | ||
| codecov_upload.sh | ||
| etcd_version_annotations.txt | ||
| fix.sh | ||
| fuzzing.sh | ||
| genproto.sh | ||
| install-marker.sh | ||
| measure-testgrid-flakiness.sh | ||
| README | ||
| release_mod.sh | ||
| release.sh | ||
| sync_go_toolchain_directive.sh | ||
| test_images.sh | ||
| test_lib.sh | ||
| test.sh | ||
| update_dep.sh | ||
| update_proto_annotations.sh | ||
| updatebom.sh | ||
| verify_genproto.sh | ||
| verify_go_versions.sh | ||
| verify_proto_annotations.sh | ||
scripts for etcd development