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
discard 164e2ee2 Minor: Regenerated License File for
8c0d14e1b642e73a3cc734621ec7c103b71bddeb
add 3251b798 Bump com.microsoft.playwright:playwright from 1.53.0 to 1.54.0
add 23c23c48 Minor: Regenerated License File for
3251b79828bdb9a3820cddabeaf75ac3a7dd6dfb
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 (164e2ee2)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(23c23c48)
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(-)
