The GitHub Actions job "Required Checks" on texera.git/renovate/github-actions has succeeded. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: 92dae724f95b3ae422e7c8c4be8edf695754b1ff / Xinyuan Lin <[email protected]> fix(ci): drop the Python 3.14 bump and sync the frontend Node pin Python 3.14 breaks amber-integration on macOS. numpy is pinned at 2.1.0, which predates 3.14 and ships no cp314 wheel, so uv builds it from source and Apple clang 21 rejects its C++: x Failed to build `numpy==2.1.0` `-> Call to `mesonpy.build_wheel` failed (exit status: 1) ../numpy/_core/src/umath/string_fastsearch.h:132:5: error: no type named ... 11 errors generated. numpy, pandas and pyarrow are deliberately frozen (.github/ renovate.json5) because they sit on the Arrow IPC path between the JVM engine and the Python workers, so the Python floor cannot move until they do. pyamber's own matrix is ["3.11", "3.12", "3.13"] for the same reason -- 3.14 would have tested the engine against a Python the workers do not support. The Linux build happens to succeed (Benchmarks is ubuntu-only and went green on 3.14), but amber-integration runs a macOS leg, so the bump cannot stand. The Node bump is kept and completed. Renovate only rewrote the `with: node-version:` literal in the pyright-language-service job; the frontend job takes its version from a bare matrix list item the github-actions manager does not match, so it stayed on 24.10.0 and falsified the "Matches the frontend job's pinned Node." comment directly above the bumped line. Both are now 24.19.0. This invalidates the frontend yarn cache once, since the key is keyed on matrix.node-version. Report URL: https://github.com/apache/texera/actions/runs/31470725603 With regards, GitHub Actions via GitBox
