This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch update-license-files
in repository https://gitbox.apache.org/repos/asf/storm.git
discard 6e4ebd61f Regenerate license files after dependency changes
add da34288ac build(deps-dev): bump
com.github.eirslett:frontend-maven-plugin
add 2dda898c1 Merge pull request #8954 from
apache/dependabot/maven/com.github.eirslett-frontend-maven-plugin-2.0.2
add b35e276a4 Regenerate license files after dependency changes
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 (6e4ebd61f)
\
N -- N -- N refs/heads/update-license-files (b35e276a4)
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:
storm-webapp/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
