Skip to content

docs: clarify release checklist branch#2105

Open
Zakharden wants to merge 2 commits into
helm:mainfrom
Zakharden:docs/release-checklist-v4
Open

docs: clarify release checklist branch#2105
Zakharden wants to merge 2 commits into
helm:mainfrom
Zakharden:docs/release-checklist-v4

Conversation

@Zakharden
Copy link
Copy Markdown

@Zakharden Zakharden commented May 11, 2026

Summary

Update the maintainer release checklist so the branch used for major/minor release work is explicit instead of being hardcoded to main.

The checklist now defines DEVELOPMENT_BRANCH, keeps main as the default for Helm 4 and later releases, and documents dev-v3 for Helm 3 release work.

Fixes #1917.

Validation

  • corepack yarn install --frozen-lockfile
  • corepack yarn build
  • git diff --check HEAD~1 HEAD
  • rg -n "from main|off main|cherry-picking from main|git checkout main|upstream/main|DEVELOPMENT_BRANCH|dev-v3" community/release_checklist.md

@Zakharden Zakharden force-pushed the docs/release-checklist-v4 branch 2 times, most recently from ae94bf4 to 8259b44 Compare May 15, 2026 12:12
Signed-off-by: Zakhar Dvurechensky <72825626+Zakharden@users.noreply.github.com>
@Zakharden Zakharden force-pushed the docs/release-checklist-v4 branch from 8259b44 to 473d3bb Compare May 19, 2026 21:25
@Zakharden
Copy link
Copy Markdown
Author

This PR is still blocked by workflow/action state. I can rebase/update if needed, but right now only maintainer/CI rerun is needed. Please ping me if you want me to push a trivial follow-up.

@Zakharden
Copy link
Copy Markdown
Author

Thanks, maintainer-side checks are the only blocker here. No code changes were made from my side.

Please rerun the remaining action-required CI when possible so we can confirm readiness for merge.

@Zakharden
Copy link
Copy Markdown
Author

I’ve finished the open follow-up loop for this PR and there are no code changes pending on my side (last head unchanged in scope). This is currently blocked by workflow/action state () on maintainer side; could you rerun the required checks and/or review when convenient.

@Zakharden
Copy link
Copy Markdown
Author

I’ve completed the PR updates from my side and there are no further code changes pending. This PR currently remains blocked by action/maintainer review state. Please rerun the necessary checks/review flow and I’ll respond immediately to anything still requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update release checklist to reflect dev-v3 branch

2 participants