This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_license_file_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/stormcrawler.git
omit f0fab40c Minor: Regenerated License File for
77dbbd479c875e2985e1e78b7fc35a114fa39ee6
add 9eef525e Bump com.microsoft.playwright:playwright from 1.57.0 to
1.58.0 (#1801)
add e12a5d9c Minor: Regenerated License File for
9eef525ed42ee3618a3c5e333732719db8034f67
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 (f0fab40c)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(e12a5d9c)
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:
THIRD-PARTY.txt | 6 +++---
external/playwright/pom.xml | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
