aglinxinyuan commented on PR #8313:
URL: https://github.com/apache/texera/pull/8313#issuecomment-5502609447
Pushed b165cebe on top of the bot's commit to fix the failing `pyamber
(ubuntu-latest, 3.12)` leg.
**Root cause** — `transformers` is a *direct* dep (it lives in
`amber/operator-requirements.txt`), so the bump has to be mirrored in
`amber/LICENSE-binary-python`. The license drift check blocked on:
```
DRIFT (direct) Python packages — claimed versions differ from bundled:
~ transformers: LICENSE-binary=5.5.0 bundled=5.10.1 → update in
amber/LICENSE-binary-python
ACTION REQUIRED
Update amber/LICENSE-binary-python to match the bundled versions. Direct
deps always block CI — a version bump may carry license changes.
```
Only the 3.12 leg goes red because `build.yml` gates both the `pip-licenses`
manifest step and the check itself with `if: matrix.python-version == '3.12'` —
3.11 and 3.13 skip it and pass regardless, which makes the failure look
narrower than it is.
**Fix** — one line: `transformers==5.5.0` → `transformers==5.10.1`. It stays
in the Apache-2.0 section, since PyPI still reports `Apache 2.0 License` for
5.10.1.
The other 22 drift lines in that same output (`huggingface-hub`, `hf-xet`,
`regex`, `packaging`, …) are all transitive, and therefore informational only
under the PR-mode `--ignore-transitive-version` flag — the nightly exact-match
job on `main` is what refreshes those, so I deliberately left them untouched
here.
**Verification** — before pushing, I re-ran `check_binary_deps.py` locally
against a `pip-licenses` manifest carrying CI's exact bundled versions, both
with and without the fix:
| `amber/LICENSE-binary-python` claims | result |
| --- | --- |
| `transformers==5.5.0` (before) | `DRIFT (direct)` → exit 1, byte-identical
to CI's message |
| `transformers==5.10.1` (after) | `OK: 110 Python packages match
LICENSE-binary` → exit 0 |
All six `pyamber` legs are now green across both `Required Checks` and
`backport (release/v1.3)` — the backport run had been failing on this same step
and needs no separate fix. `amber-integration` is still running.
Generated-by: Claude Code (Opus 5)
--
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]
