From c86b2772ceedbd8aa2153774097c6b06b7ead189 Mon Sep 17 00:00:00 2001 From: Samuel Karp Date: Tue, 22 Oct 2024 15:57:26 -0700 Subject: [PATCH] docs: update min version for deprecation warnings While some warnings were available in earlier versions, the first "complete" implementation was in 1.7.12 and 1.6.27. https://github.com/containerd/containerd/issues/9312 tracks that initial set of warnings. Signed-off-by: Samuel Karp --- docs/containerd-2.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/containerd-2.0.md b/docs/containerd-2.0.md index 7a8a52721..006f2fb68 100644 --- a/docs/containerd-2.0.md +++ b/docs/containerd-2.0.md @@ -76,7 +76,7 @@ Deprecations warnings have been added to the `ServerResponse` for the introspect To ease containerd 2.0 transition, the community has moved to backport this feature to containerd 1.6 and 1.7 release branches to give users another tool to identify the sticking points for migrating containerd versions. -Administrators whose workloads are running on containerd versions >= 1.6.25, >= 1.7.9 can query their containerd server to receive warnings for features marked for deprecation and are in the critical path. With the `ctr` client, users can run `ctr deprecations list`. +Administrators whose workloads are running on containerd versions >= 1.6.27, >= 1.7.12 can query their containerd server to receive warnings for features marked for deprecation and are in the critical path. With the `ctr` client, users can run `ctr deprecations list` (and optionally pass `--format json` for machine-readable output). ## What's breaking