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


 discard a79d532f Minor: Regenerated License File for 
ca7196295d21c50e182c0c63fefa2bb368a4aeb6
     add 00bca0d0 build(deps): bump junit.version from 6.1.2 to 6.1.3 (#2054)
     add 95a9e35e Minor: Regenerated License File for 
00bca0d0a904d3a3bb7a6d84c31fc3ffc9c9e35b

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   (a79d532f)
            \
             N -- N -- N   refs/heads/regenerate_license_file_after_dep_upgrade 
(95a9e35e)

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:
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to