aglinxinyuan commented on PR #6181:
URL: https://github.com/apache/texera/pull/6181#issuecomment-4888215215

   `assertj-core` is test-only (`% Test`) in all five services, so it never 
ships in the binary distribution — no `LICENSE-binary` sync needed (the green 
`build / platform` legs confirm the direct-dep license check is happy).
   
   **Local** — bumped `assertjVersion` to `3.27.7` and ran the only spec that 
touches AssertJ, `WorkflowCompilationResourceSpec` (workflow-compiling-service):
   
   ```
   [info] * assertj-core-3.27.7.jar
   [info] Run completed in 3 seconds, 210 milliseconds.
   [info] Tests: succeeded 3, failed 0, canceled 0, ignored 0, pending 0
   [info] All tests passed.
   ```
   
   The only API in use is `assertThat(...).isEqualTo(...)` / `.isTrue`, 
unchanged across 3.24 → 3.27, so nothing else in the tree is affected.
   
   **CI** — the red `Required Checks` wasn't a real failure. The labeler's 
`labeled` event started a second `pull_request` run that superseded the first 
via `cancel-in-progress`, and the cancelled run's `always()` aggregation 
reported failure off the cancelled `precheck`. The live run had already passed 
everything; I re-ran the superseded run (and the stale `Benchmarks` cancel) so 
both go green.
   


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