We build and release Helm CLI from our downstream repo. Ideally, the release branches should be identical to their upstream counterparts, but the reality tolerates a bit of divergence, e.g in domain of testing/packaging/CI. However, the number of downstream introduced commits should be kept on minimum, eventually submitting them upstream. Furthermore, a low number of additional commits allow easy releasing of upcoming versions.

The current situation at the downstream repository is pretty much unsustainable: release-3.1 branch diverged so much that GitHub cannot even display all differences to the upstream. Clearly, we did not introduce 1313 new commits - it looks that they are result of some wrongly-went git rebase, but the current states give us a lot of headache, when syncing from the upstream is needed.

Actions needed:

• Identify our added commits
• Apply them on the top of upstream release-3.1 branch
• Recreate downstream release-3.1 branch