The GitHub Actions job "Required Checks" on texera.git/dependabot/sbt/org.jooq-jooq-3.21.6 has succeeded. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: 4b4a985794d193a062c4c8f7602aa8faff5014c9 / Xinyuan Lin <[email protected]> fix(deps): cap org.jooq:jooq at 3.19.36 for Java 17 compatibility jOOQ 3.20+ Open Source Edition is compiled to Java 21 bytecode (class file version 65), but Texera builds and runs on Java 17 across every CI matrix. Bumping to 3.21.6 therefore failed at test runtime with UnsupportedClassVersionError (build / amber-integration and build / platform (computing-unit-managing-service)). Cap all jooq artifacts at 3.19.36 -- the latest release that still targets Java 17 -- in amber, computing-unit-managing-service, common/dao and the jooq-codegen build plugin. jooq-codegen must move in lockstep with the runtime: the generated jOOQ code must not call constructors that the 3.19 runtime deprecates, since javac runs with -Xlint:deprecation -Werror (a 3.16 codegen against a 3.19 runtime fails DAO/Compile). The 42.7.4 pgjdbc codegen pin still applies (the KEY_SEQ fix is only in jOOQ 3.20+). Resync the binary license metadata across all seven service dists: - jooq bullet 3.16.23 -> 3.19.36 in every LICENSE-binary. - amber drops com.sun.activation.jakarta.activation, which is no longer bundled: jooq's jakarta.xml.bind-api dependency became optional in 3.19, so amber's xml.bind-api falls back to 2.3.2 (no transitive activation). - Regenerate NOTICE-binary via bin/licensing/generate_notice_binary.py (io.r2dbc.r2dbc-spi 0.9.0 -> 1.0.0 everywhere; amber also reflects the xml.bind-api and activation changes). Report URL: https://github.com/apache/texera/actions/runs/28907559549 With regards, GitHub Actions via GitBox
