Skip to content

asf: protect the main-hudi-0x release branch#842

Closed
vinishjail97 wants to merge 1 commit into
apache:mainfrom
vinishjail97:asf-protect-main-hudi-0x
Closed

asf: protect the main-hudi-0x release branch#842
vinishjail97 wants to merge 1 commit into
apache:mainfrom
vinishjail97:asf-protect-main-hudi-0x

Conversation

@vinishjail97

Copy link
Copy Markdown
Contributor

Adds branch protection for main-hudi-0x, mirroring main's rule (1 required approving review).

Why

Per the [DISCUSS] rc1 for XTable 0.4.0 thread, 0.4.0 is cut from the Hudi 0.x line (main-hudi-0x) while v9 (#834) + indexing head to 0.5.0 on main. That release branch should have the same protection as main.

Why this is a separate PR against main

ASF INFRA reads .asf.yaml from the repository's default branch (main) only. The companion change on the branch itself (#841) is inert for protection purposes, so this one-line change to main is what actually enables it. INFRA applies it within a couple of minutes of merge.

Follow-up option: once #841's CI reports on main-hudi-0x, we can add required_status_checks here too.

🤖 Generated with Claude Code

main-hudi-0x is the Hudi 0.x line that 0.4.0 is cut from. Mirror main's
protection rule (1 required approving review) for it. .asf.yaml is read
by ASF INFRA from the default branch (main), so this must land on main
to take effect.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vinishjail97 vinishjail97 marked this pull request as ready for review July 9, 2026 18:51
@vinishjail97

Copy link
Copy Markdown
Contributor Author

Closing as not required. Per the [DISCUSS] rc1-for-0.4.0 thread, we're dropping the dependency-named main-hudi-0x branch in favor of a standard version-keyed release line: main-hudi-0x has been renamed to branch-0.4, and 0.4.0 will be cut from main with patch fixes cherry-picked onto branch-0.4 (the Spark branch-3.5 model). This PR added .asf.yaml protection specifically for main-hudi-0x, which no longer exists. Branch protection / required status checks for branch-0.4 can be added separately at RC time if the community wants it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant