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

potiuk pushed a change to branch add-apply-commit-feature-to-docs-buildiung
in repository https://gitbox.apache.org/repos/asf/airflow.git


    omit e0414e61a9e Add possibility to apply a commit with patch to docs when 
publishing
     add b8e44e78b44 Fixing mypy checks for devel-common on main (#53666)
     add 82c2a0ffdda Bump the core-ui-package-updates group across 1 directory 
with 13 updates (#53608)
     add a16c02c780f Add possibility to apply a commit with patch to docs when 
publishing

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   (e0414e61a9e)
            \
             N -- N -- N   
refs/heads/add-apply-commit-feature-to-docs-buildiung (a16c02c780f)

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/publish-docs-to-s3.yml           |    2 +-
 .../auth/managers/simple/ui/package-lock.json      | 1717 +++++++--------
 .../auth/managers/simple/ui/package.json           |   26 +-
 .../auth/managers/simple/ui/pnpm-lock.yaml         | 2196 ++++++++++----------
 .../src/tests_common/test_utils/watcher.py         |    6 +-
 5 files changed, 2015 insertions(+), 1932 deletions(-)

Reply via email to