kz930 opened a new pull request, #8355: URL: https://github.com/apache/texera/pull/8355
### What changes were proposed in this PR? One line. `amber/LICENSE-binary-python` records typing-extensions at 4.14.1 and 4.16.0 is what gets installed, so the check that compares the two fails. It is a direct dependency, and a direct dependency whose recorded version has drifted blocks the Python 3.12 leg outright. That leg went red repo-wide on 2 September, on every pull request rather than only on whichever runs next, which is why this is on its own rather than inside the change that first hit it. ### Any related issues, documentation, discussions? The same one-line change is also in #8327, so that branch is not left red while this waits; the two are byte-identical and will merge without a conflict. Refreshing the record is the remedy each time this surfaces (#7285, #8292). It does not explain why a pinned package drifted at all: `amber/requirements.txt` pins `typing_extensions==4.14.1`, and that pin is not binding on the passes installed after it. #8354 covers that. ### How was this PR tested? The failing step is `Check installed Python packages against per-module LICENSE-binary files`, which runs on the 3.12 leg and is what this PR's own CI exercises. ### Was this PR authored or co-authored using generative AI tooling? 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]
