This is an automated email from the ASF dual-hosted git repository.

vincbeck pushed a change to branch backport-a26f9f9-v3-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


    omit fecc77f1445 [v3-4-test] Fix missing and incorrect endpoints in the API 
permission reference (#74871) (cherry picked from commit 
a26f9f9926c29d9126fc5ca5f33b4e724c8bc509)
    omit 2c6493b7636 [v3-4-test] Render XCom values on the API server without 
rebuilding objects (#74829) (#75088)
    omit a658a2458dd [v3-4-test] Bump the github-actions-updates group with 10 
updates (#74880) (#75021)
     new 5e8d4c6de02 [v3-4-test] Fix missing and incorrect endpoints in the API 
permission reference (#74871) (cherry picked from commit 
a26f9f9926c29d9126fc5ca5f33b4e724c8bc509)

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   (fecc77f1445)
            \
             N -- N -- N   refs/heads/backport-a26f9f9-v3-4-test (5e8d4c6de02)

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.

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.


Summary of changes:
 .github/workflows/airflow-e2e-tests.yml            |  4 +-
 .github/workflows/asf-allowlist-check.yml          |  2 +-
 .github/workflows/basic-tests.yml                  |  2 +-
 .github/workflows/ci-amd.yml                       | 12 +--
 .github/workflows/ci-arm.yml                       | 12 +--
 .github/workflows/ci-duration-monitor.yml          |  2 +-
 .github/workflows/ci-image-build.yml               | 16 ++--
 .github/workflows/ci-image-checks.yml              | 10 +--
 .github/workflows/ci-notification.yml              |  4 +-
 .github/workflows/codeql-analysis.yml              |  6 +-
 .github/workflows/e2e-flaky-tests-report.yml       |  2 +-
 .github/workflows/finalize-tests.yml               |  2 +-
 .github/workflows/generate-constraints.yml         |  2 +-
 .github/workflows/helm-tests.yml                   |  2 +-
 .github/workflows/k8s-tests.yml                    |  6 +-
 .github/workflows/notify-uv-lock-conflicts.yml     |  2 +-
 .github/workflows/openlineage-e2e-compat-tests.yml |  2 +-
 .github/workflows/prod-image-build.yml             |  8 +-
 .github/workflows/publish-docs-to-s3.yml           | 20 ++---
 .github/workflows/push-image-cache.yml             |  2 +-
 .github/workflows/registry-backfill.yml            |  2 +-
 .github/workflows/registry-build.yml               |  4 +-
 .github/workflows/registry-tests.yml               |  2 +-
 .github/workflows/release-constraints.yml          |  2 +-
 .../workflows/release_single_dockerhub_image.yml   |  4 +-
 .../scheduled-verify-release-calendar.yml          |  2 +-
 .github/workflows/ts-sdk-release.yml               |  8 +-
 .github/workflows/ui-e2e-tests.yml                 |  6 +-
 .../update-constraints-on-push-stable.yml          |  2 +-
 .github/workflows/update-constraints-on-push.yml   |  2 +-
 .../api_fastapi/core_api/routes/public/xcom.py     | 23 ++++--
 .../serialization/definitions/operatorlink.py      | 14 +++-
 .../src/airflow/serialization/stringify.py         | 82 ++++---------------
 .../core_api/routes/public/test_xcom.py            | 65 +---------------
 .../tests/unit/serialization/test_operatorlink.py  | 21 -----
 .../tests/unit/serialization/test_stringify.py     | 91 ++--------------------
 scripts/ci/prek/fab_permissions_doc.py             | 13 +---
 37 files changed, 130 insertions(+), 331 deletions(-)

Reply via email to