This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch
regenerate_license_file_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/stormcrawler.git
omit de6ba59d Minor: Regenerated License File for
9b72b5a58dbda17d6f2ff2880f3bdbbc7be72a7c
add e4d30f71 build(deps): bump org.jsoup:jsoup from 1.22.2 to 1.23.1
add 00ec1bd4 Minor: Regenerated License File for
e4d30f71bd496bc86f5c1cdd7030967c57956a9c
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 (de6ba59d)
\
N -- N -- N refs/heads/regenerate_license_file_after_dep_upgrade
(00ec1bd4)
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 | 2 +-
core/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
