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 b104e66d2 Regenerate license files after dependency changes
add 97b9a6f8e build(deps): bump
com.fasterxml.jackson.core:jackson-databind (#9115)
add a093402dc build(deps): bump org.codehaus.mojo:exec-maven-plugin (#9116)
add 577f5c545 build(deps): bump
org.apache.maven.plugins:maven-surefire-report-plugin (#9117)
add e707db037 build(deps): bump
io.github.git-commit-id:git-commit-id-maven-plugin (#9119)
add b04ba6749 build(deps): bump zookeeper.version from 3.9.5 to 3.9.6 in
/examples (#9120)
add 3524ea9b7 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 (b104e66d2)
\
N -- N -- N refs/heads/update-license-files (3524ea9b7)
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:
DEPENDENCY-LICENSES | 1 +
pom.xml | 8 ++++----
2 files changed, 5 insertions(+), 4 deletions(-)
