DanielLeens commented on PR #11812: URL: https://github.com/apache/seatunnel/pull/11812#issuecomment-5447331047
@nzw921rx Your understanding is correct on both points — confirmed against the current head just now. **CI status**: current head `65e63c38` is fully green. The apache-side `Build` check (pointer to the fork's real CI run) completed with `conclusion: success`, and so did `Notify test workflow` and `labeler`. I also checked the fork's own Actions run behind it (`goutamadwant/seatunnel` run `33032927653`) directly — success there too, no lingering flaky-container/rate-limit failures like the earlier rounds. So yes, CI has actually passed on this head, not just "looks clean." **Rebase/sync**: also confirmed — comparing `dev...65e63c38` shows `behind_by: 0`, `ahead_by: 16`. This branch is not behind `dev` at all (davidzollo's upstream update on 2026-08-25 already covered that), so there's no divergence and no rebase needed right now. One thing worth noting so it doesn't cause confusion: GitHub currently shows this PR's merge state as "Unstable" rather than "Clean." That's not a real CI/code signal — it's caused by an internal repo-automation workflow (`Label-when-reviewed`, triggered on review events) sitting in `action_required` because it needs a maintainer to approve it running for an external-fork PR. It has nothing to do with the classloader-release fix or the test suite, and no action is needed on your side for it. Net: no further contributor action needed here — CI is green, no rebase required, and my source-side approval from the classloader logic review still stands (only a clean `dev` merge landed since then, no functional changes). This is ready for a maintainer to do the final merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
