This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch
dependabot/pip/dev/breeze/v2-11-test/hatch-1.15.1
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard ce50268dc7f Bump hatch from 1.14.1 to 1.15.1 in /dev/breeze
add 880f29845a4 update null event values to empty string in downgrade for
migration revision_id d75389605139 (#57131)
add b8ca89a93b1 Bump hatch from 1.14.1 to 1.15.1 in /dev/breeze
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 (ce50268dc7f)
\
N -- N -- N
refs/heads/dependabot/pip/dev/breeze/v2-11-test/hatch-1.15.1 (b8ca89a93b1)
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:
..._9_0_add_run_id_to_audit_log_table_and_change_event_name_length.py | 4 ++--
docs/apache-airflow/img/airflow_erd.sha256 | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
