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 234b59b7 Minor: Regenerated License File for
216f48fed182e9a792cf3801533565649f17f421
add 1c197968 Bump de.thetaphi:forbiddenapis from 3.9 to 3.10
add 0adc2538 Bump org.codehaus.mojo:license-maven-plugin from 2.6.0 to
2.7.0
add 64f1dc4b Bump git-code-format-maven-plugin.version from 5.3 to 5.4
add a733e877 Bump selenium.version from 4.35.0 to 4.36.0
add 30b9ab29 Bump org.apache.maven.plugins:maven-enforcer-plugin from
3.6.1 to 3.6.2
add cf5962bb Bump aws.version from 1.12.791 to 1.12.792
add 3153dbb2 Minor: Regenerated License File for
0adc2538db467be50b317aad08e41346c6f186bd
add 2677eae0 Minor: Regenerated License File for
a733e8775bc7052319afce61397c97f551c5d6eb
add 130c0a35 Bump junit.version from 5.13.4 to 6.0.0
add ee0ab542 Minor: Regenerated License File for
130c0a354e697c091264edc7cf714c0b88c69fc0
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 (234b59b7)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(ee0ab542)
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 | 51 +++++++++++++++++++++++------------------------
external/aws/pom.xml | 2 +-
external/selenium/pom.xml | 2 +-
pom.xml | 10 +++++-----
4 files changed, 32 insertions(+), 33 deletions(-)
