Update containerd to v1.5.0-beta1 and revendor #946
Merged
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.
containerd has an extensive dependency tree, and this is a large jump from v1.3.2, so this single-line change leads to a lot of churn in both go.mod and vendoring, particularly for the 'test' submodule.
Switching from v1.3.2 to v1.5.0-beta1 is too large a comparison for GitHub to usefully show, particularly because it goes down the release-1.3 branch back to September 2019, and then forwards to near current master.
This change is being done to get containerd/containerd#4395, which deforked some code from Microsoft/go-winio. A structure type used by that deduplicated has changed in go-winio recently, and so pulling in both older containerd and newer go-winio leads to compile failures.
The motivation for this change is that #901 requires newer go-winio; the same PR as the API change; as it happens.