mengw15 opened a new issue, #8374:
URL: https://github.com/apache/texera/issues/8374
### What happened?
`build / pyamber (ubuntu-latest, 3.12)` fails its "Check installed Python
packages against per-module LICENSE-binary files" step on every pull request,
and on `main` itself — the last four `Required Checks` runs on `main` are all
red.
```
DRIFT (direct) Python packages — claimed versions differ from bundled:
~ typing-extensions: LICENSE-binary=4.14.1 bundled=4.16.0
ACTION REQUIRED
Update amber/LICENSE-binary-python to match the bundled versions. Direct
deps always block CI — a version bump may carry license changes.
```
`typing-extensions` is a direct dependency, so the drift hard-fails rather
than being informational. The transitive entries printed alongside it are
advisory and refreshed by the nightly exact-match check.
Re-running does not help: the resolver picks up 4.16.0 every time, so this
blocks the queue until `amber/LICENSE-binary-python` is refreshed. The fix is
one line — `amber/LICENSE-binary-python:358`, `typing-extensions==4.14.1` →
`4.16.0` — pending a check that 4.16.0 carries no license change.
This is the same failure mode as the `cloudpickle` drift fixed in #8293 last
week, with a different package.
Filed separately from #7285 rather than as a comment on it: that issue is
the weekly aggregate opened and re-used by `license-binary-checker.yml`
(matched by its fixed title, `cron: '0 11 * * 1'`), so it does not name the
offending dependency and will not update until next Monday. #7285 was also
taken by @anthonychengit on 26 Aug; this one is scoped to the single package
currently blocking CI.
### How to reproduce?
Open or re-run any PR and look at `build / pyamber (ubuntu-latest, 3.12)`.
Example: #8096,
[run](https://github.com/apache/texera/actions/runs/33710669719) — the license
step fails and every later step is skipped.
### Version/Branch
main
--
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]
