From 127211ed052e2ac1f0aca583f8be52a316b256a3 Mon Sep 17 00:00:00 2001 From: Akanksha Trehun Date: Mon, 13 Jul 2026 20:31:04 +0530 Subject: [PATCH] docs(CONTRIBUTING): use actual latest release version in example Use 4.2.3 (actual latest release) instead of 4.0.0 in the milestone version example to avoid misleading contributors. Signed-off-by: Akanksha Trehun --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6e7cf75f2..0c72ac792 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -118,9 +118,9 @@ It is also worth asking on the Slack channels. We use milestones to track progress of specific planned releases. -For example, if the latest currently-released version is `4.0.0`, an issue/PR which pertains to a +For example, if the latest currently-released version is `4.2.3`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: -`4.0.1` or `4.1.0`. +`4.2.4` or `4.3.0`. Issues and PRs which are deemed backwards-incompatible may be added to the discussion items for Helm 5 with [label:v5.x](https://github.com/helm/helm/labels/v5.x). An issue or PR that we are not