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 e9d85fe6 Minor: Regenerated License File for
342fa11b8e87edab09992a53657e656f21c6407f
add b12b7f53 Bump com.mysql:mysql-connector-j from 9.3.0 to 9.5.0 (#1778)
add 358b5f38 Minor: Regenerated License File for
b12b7f53eaadee090c0c3810e532020c6e88f05d
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 (e9d85fe6)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(358b5f38)
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 | 4 ++--
pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
