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 9b7993ad Minor: Regenerated License File for
ed312c64784e45c340291a7c903876b5f146df64
add d2fc47a2 Bump selenium.version from 4.36.0 to 4.37.0
add 6063aff7 Minor: Regenerated License File for
d2fc47a22e1f37a857c684f69f7f522cf6ecfc67
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 (9b7993ad)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(6063aff7)
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 | 38 +++++++++++++++++++-------------------
external/selenium/pom.xml | 2 +-
2 files changed, 20 insertions(+), 20 deletions(-)
