This is an automated email from the ASF dual-hosted git repository.
vatsrahul1001 pushed a change to branch backport-8401a19-v3-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 09929ff3149 [v3-4-test] Run the lang-SDK native Dag tests on
Kubernetes (#75930)
add 6bc7af8fca5 [v3-4-test] Reject non-object JSON files when importing
variables (#75384) (#75950)
add 6dc69409a84 [v3-4-test] Refuse to publish constraints when the branch
moved during generation (#75989) (#75990)
add a523eae3391 [v3-4-test] Run the lang-SDK native Dag tests on
Kubernetes (#75930)
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 (09929ff3149)
\
N -- N -- N refs/heads/backport-8401a19-v3-4-test (a523eae3391)
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:
.github/workflows/update-constraints-on-push.yml | 28 ++++++++
.../pages/Variables/ImportVariablesForm.test.tsx | 83 ++++++++++++++++++++++
.../ui/src/pages/Variables/ImportVariablesForm.tsx | 12 +++-
...UALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md | 6 ++
4 files changed, 126 insertions(+), 3 deletions(-)
create mode 100644
airflow-core/src/airflow/ui/src/pages/Variables/ImportVariablesForm.test.tsx
