You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@texera.apache.org by gi...@apache.org on 2026/09/16 18:15:39 UTC
(texera) branch gh-readonly-queue/release/v1.3/pr-8549-84b6c9086ef2a2627098e21ee222e3c4567d6fbb created (now d3f0529bd0)
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a change to branch gh-readonly-queue/release/v1.3/pr-8549-84b6c9086ef2a2627098e21ee222e3c4567d6fbb
in repository https://gitbox.apache.org/repos/asf/texera.git
at d3f0529bd0 fix(amber, v1.3): refresh typing-extensions in LICENSE-binary-python (#8549)
This branch includes the following new commits:
new d3f0529bd0 fix(amber, v1.3): refresh typing-extensions in LICENSE-binary-python (#8549)
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(texera) 01/01: fix(amber, v1.3): refresh typing-extensions in LICENSE-binary-python (#8549)
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/release/v1.3/pr-8549-84b6c9086ef2a2627098e21ee222e3c4567d6fbb
in repository https://gitbox.apache.org/repos/asf/texera.git
commit d3f0529bd0d824035bcfbd46c6d6c8a2a64bd1f4
Author: Meng Wang <me...@uci.edu>
AuthorDate: Wed Sep 16 18:15:16 2026 +0000
fix(amber, v1.3): refresh typing-extensions in LICENSE-binary-python (#8549)
### What changes were proposed in this PR?
Backport of #8375 to `release/v1.3`: a clean cherry-pick of its squash
commit, no adaptations. `typing-extensions` is a direct dependency and
resolves to 4.16.0, while this branch's `amber/LICENSE-binary-python`
still claims 4.14.1. Direct-dependency drift hard-fails the license
check, so `build / pyamber (ubuntu-latest, 3.12)` is red on this branch
(run 34558321985, on #8500's merge) and the `backport (release/v1.3)`
check of every pyamber PR fails the same way (e.g. #8432). Re-running
does not help: the resolver picks 4.16.0 each time.
`amber/requirements.txt` and `amber/operator-requirements.txt` on this
branch are identical to `main`'s, and after this change the manifest is
byte-identical to `main`'s, where the same check is green.
Opened manually by the v1.3 release manager: #8375's `release/*` labels
were removed before it merged, so the automated backport never ran.
Source: 16da22bab8d508e8aeebb436e2259f82d0ce7148
### Any related issues, documentation, discussions?
Backport of #8375. Originally linked #8374.
### How was this PR tested?
The check itself runs in CI on this PR: a green `build / pyamber
(ubuntu-latest, 3.12)` is the confirmation. Locally, the branch is
verified to be exactly the squash commit cherry-picked onto
`release/v1.3` (one file, one line), and the resulting
`amber/LICENSE-binary-python` is byte-identical to `main`'s.
### Was this PR authored or co-authored using generative AI tooling?
Yes. Generated-by: Claude Code (claude-fable-5-1)
---
amber/LICENSE-binary-python | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/amber/LICENSE-binary-python b/amber/LICENSE-binary-python
index 976c2f702d..2d3c3cb64b 100644
--- a/amber/LICENSE-binary-python
+++ b/amber/LICENSE-binary-python
@@ -355,7 +355,7 @@ Dependencies under the Python Software Foundation License
Python packages:
- aiohappyeyeballs==2.7.1
- matplotlib==3.11.1
- - typing-extensions==4.14.1
+ - typing-extensions==4.16.0
--------------------------------------------------------------------------------
Dependencies under the MIT-CMU License