This is an automated email from the ASF dual-hosted git repository.
ash pushed a change to branch generate-task-jwt-tokens
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 3170f6e9074 fixup! Add JWT validation and generation machinery for the
Task Execution API to use
discard 87f577ad9ba Add compat for Airflow 2.10 for Edge Provider
discard 4a6aa37bda5 Add JWT validation and generation machinery for the Task
Execution API to use
add 37b03c1d541 Move XComOperatorLink to serialized_objects as only API
server uses it (#47674)
add a75517b1051 Add upper bound for attrs - 25.2.0 broke main (#47683)
add ee18cd80e35 Add JWT validation and generation machinery for the Task
Execution API to use
add 1f51dcce959 Add compat for Airflow 2.10 for Edge Provider
add ef6c93b78a3 fixup! Add JWT validation and generation machinery for the
Task Execution API to use
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (3170f6e9074)
\
N -- N -- N refs/heads/generate-task-jwt-tokens (ef6c93b78a3)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
airflow/serialization/serialized_objects.py | 38 +++++++++++++++++++++-
hatch_build.py | 4 ++-
task-sdk/pyproject.toml | 4 ++-
.../airflow/sdk/definitions/baseoperatorlink.py | 38 ----------------------
tests/serialization/test_dag_serialization.py | 2 +-
5 files changed, 44 insertions(+), 42 deletions(-)
