DanielLeens commented on PR #12335:
URL: https://github.com/apache/seatunnel/pull/12335#issuecomment-5881997212

   Following up on my own note above, since the condition I was waiting for has 
now happened: the branch was pushed and the head SHA changed (`63c14e7a` -> 
`fe946b0f893334f`, via `Merge remote-tracking branch 'upstream/dev'`).
   
   I diffed `63c14e7a...fe946b0f893334f` directly: it's 44 files, all outside 
this PR's own scope (other connectors' docs, JDBC/CDC/Redis/SMB/Fluss files, 
dist license files, etc.) — nothing under `seatunnel-transforms-v2` or the 
vector/SQL docs this PR touches. So the merge landed cleanly with no conflicts 
silently resolved into the vector-buffer fix itself, and my original approval 
(on `03e7a6fa`, the commit that actually contains the fix) still stands 
unchanged.
   
   CI on this new head is still running as I write this (`Code style` in 
progress, `changes` queued, `Dead links`/`License header` green so far) — I'll 
take one more look once it finishes to confirm the `Build` check is green 
before this is ready to merge. No action needed from you in the meantime.
   


-- 
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]

Reply via email to