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 0f99ec34 Minor: Regenerated License File for
cf5962bb068ec566e40b8cfb491b9134f62adf48
omit cf5962bb Bump aws.version from 1.12.791 to 1.12.792
omit 30b9ab29 Bump org.apache.maven.plugins:maven-enforcer-plugin from
3.6.1 to 3.6.2
add 60b336d6 Minor: Regenerated License File for
a733e8775bc7052319afce61397c97f551c5d6eb
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 (0f99ec34)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(60b336d6)
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 | 10 +++++-----
external/aws/pom.xml | 2 +-
pom.xml | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
