This is an automated email from the ASF dual-hosted git repository.
weilee pushed a change to branch backport-1ce068b-v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 529e9412066 [v3-1-test] fix(models/dag): handle pre AIP-39 DagRuns
(#58229) (cherry picked from commit 1ce068bc126ac7a352959f40c7d84a41ea5e3366)
add 8b99bd0b9bf [v3-1-test] Add one as a fallback grid value for number of
dagruns (#58680) (#58735)
add 9713dd33df6 [v3-1-test] fix(models/dag): handle pre AIP-39 DagRuns
(#58229) (cherry picked from commit 1ce068bc126ac7a352959f40c7d84a41ea5e3366)
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 (529e9412066)
\
N -- N -- N refs/heads/backport-1ce068b-v3-1-test (9713dd33df6)
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:
.../src/airflow/ui/src/layouts/Details/PanelButtons.tsx | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
