From c5e9478e0741b5cde095b6205cc9b64715c5e012 Mon Sep 17 00:00:00 2001 From: Rishav Date: Mon, 8 Jun 2026 00:05:30 +0530 Subject: [PATCH 1/7] docs: update outdated v3 references to v4 in CONTRIBUTING.md Signed-off-by: Rishav --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7aa19972f..b311f5431 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -116,14 +116,14 @@ that we're already aware of. It is also worth asking on the Slack channels. ## Milestones -We use milestones to track progress of specific planned releases. +We use milestones to track progress of specific planned releases. Helm v4 is the current stable release. -For example, if the latest currently-released version is `3.2.1`, an issue/PR which pertains to a +For example, if the latest currently-released version is `4.0.0`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: -`3.2.2` or `3.3.0`. +`4.0.1` or `4.1.0`. -Issues and PRs which are deemed backwards-incompatible may be added to the discussion items for -Helm 4 with [label:v4.x](https://github.com/helm/helm/labels/v4.x). An issue or PR that we are not +Issues and PRs which are deemed backwards-incompatible may be added to the next major version discussion +with [label:v4.x](https://github.com/helm/helm/labels/v4.x). An issue or PR that we are not sure if we will be addressing will not be added to any milestone. A milestone (and hence release) can be closed when all outstanding issues/PRs have been closed From 050782e6875fb77b4de25064e506ec162a2342cf Mon Sep 17 00:00:00 2001 From: Rishav Date: Mon, 8 Jun 2026 00:21:38 +0530 Subject: [PATCH 2/7] docs: address Copilot review comments Signed-off-by: Rishav --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b311f5431..67cec8238 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -116,15 +116,15 @@ that we're already aware of. It is also worth asking on the Slack channels. ## Milestones -We use milestones to track progress of specific planned releases. Helm v4 is the current stable release. +We use milestones to track progress of specific planned releases. Helm is the current stable release. For example, if the latest currently-released version is `4.0.0`, 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`. -Issues and PRs which are deemed backwards-incompatible may be added to the next major version discussion -with [label:v4.x](https://github.com/helm/helm/labels/v4.x). An issue or PR that we are not -sure if we will be addressing will not be added to any milestone. +Issues and PRs which are deemed backwards-incompatible may be tracked under the relevant major version discussion using the appropriate label. + +An issue or PR that we are not sure if we will be addressing will not be added to any milestone. A milestone (and hence release) can be closed when all outstanding issues/PRs have been closed or moved to another milestone and the associated release has been published. From be2e6e93d55eb050b945794233a4115a249198d8 Mon Sep 17 00:00:00 2001 From: Rishav Date: Mon, 8 Jun 2026 00:28:24 +0530 Subject: [PATCH 3/7] docs: fix version consistency in milestones section Signed-off-by: Rishav --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 67cec8238..0e3d07c5c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -116,13 +116,13 @@ that we're already aware of. It is also worth asking on the Slack channels. ## Milestones -We use milestones to track progress of specific planned releases. Helm is the current stable release. +We use milestones to track progress of specific planned releases. The current stable major release is the latest Helm version. For example, if the latest currently-released version is `4.0.0`, 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`. -Issues and PRs which are deemed backwards-incompatible may be tracked under the relevant major version discussion using the appropriate label. +Issues and PRs which are deemed backwards-incompatible may be tracked using the relevant version label for major version discussions. An issue or PR that we are not sure if we will be addressing will not be added to any milestone. From 0ee4692f14e4980267f65ceed3b899d3a5c8baee Mon Sep 17 00:00:00 2001 From: Rishav Date: Mon, 8 Jun 2026 01:38:05 +0530 Subject: [PATCH 4/7] docs: use generic version placeholders and improve label reference Signed-off-by: Rishav --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0e3d07c5c..20afc44bf 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -116,13 +116,13 @@ that we're already aware of. It is also worth asking on the Slack channels. ## Milestones -We use milestones to track progress of specific planned releases. The current stable major release is the latest Helm version. +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 -specific upcoming bugfix or feature release could fall into one of two different active milestones: -`4.0.1` or `4.1.0`. +For example, if the latest currently-released version is `X.Y.Z`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: +`X.Y.(Z+1)` or `X.(Y+1).0`. -Issues and PRs which are deemed backwards-incompatible may be tracked using the relevant version label for major version discussions. +Issues and PRs which are deemed backwards-incompatible may be added to the next major version +discussion using the relevant version label (e.g. [label:v4.x](https://github.com/helm/helm/labels/v4.x)). An issue or PR that we are not sure if we will be addressing will not be added to any milestone. From 4633bf050706705530f228029b8e79759ff0c1da Mon Sep 17 00:00:00 2001 From: Rishav Date: Mon, 8 Jun 2026 01:41:08 +0530 Subject: [PATCH 5/7] docs: use concrete example versions with labels for clarity Signed-off-by: Rishav --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 20afc44bf..d59fa5786 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -116,10 +116,11 @@ that we're already aware of. It is also worth asking on the Slack channels. ## Milestones +## Milestones + We use milestones to track progress of specific planned releases. -For example, if the latest currently-released version is `X.Y.Z`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: -`X.Y.(Z+1)` or `X.(Y+1).0`. +For example, if the latest currently-released version is `1.2.3`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: `1.2.4` (next patch) or `1.3.0` (next minor). Issues and PRs which are deemed backwards-incompatible may be added to the next major version discussion using the relevant version label (e.g. [label:v4.x](https://github.com/helm/helm/labels/v4.x)). From f6ad068c8f68c78cc94501c119513e30e2d5ace0 Mon Sep 17 00:00:00 2001 From: Rishav Bansal Date: Sun, 21 Jun 2026 18:17:35 +0530 Subject: [PATCH 6/7] Update CONTRIBUTING.md Co-authored-by: George Jenkins Signed-off-by: Rishav Bansal --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d59fa5786..cf7c1aeda 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -123,7 +123,7 @@ We use milestones to track progress of specific planned releases. For example, if the latest currently-released version is `1.2.3`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: `1.2.4` (next patch) or `1.3.0` (next minor). Issues and PRs which are deemed backwards-incompatible may be added to the next major version -discussion using the relevant version label (e.g. [label:v4.x](https://github.com/helm/helm/labels/v4.x)). +discussion using the relevant version label (e.g. [label:v5.x](https://github.com/helm/helm/labels/v5.x)). An issue or PR that we are not sure if we will be addressing will not be added to any milestone. From 840cd6316dd8fe9f83dbcddc8c388661957b9792 Mon Sep 17 00:00:00 2001 From: Rishav Bansal Date: Sun, 21 Jun 2026 18:19:33 +0530 Subject: [PATCH 7/7] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Rishav Bansal --- CONTRIBUTING.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cf7c1aeda..3f80ec6f2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -116,8 +116,6 @@ that we're already aware of. It is also worth asking on the Slack channels. ## Milestones -## Milestones - We use milestones to track progress of specific planned releases. For example, if the latest currently-released version is `1.2.3`, an issue/PR which pertains to a specific upcoming bugfix or feature release could fall into one of two different active milestones: `1.2.4` (next patch) or `1.3.0` (next minor).