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 93e2641f9 Regenerate license files after dependency changes
add 7fff662ad build(deps): bump org.rocksdb:rocksdbjni from 10.10.1.1 to
11.8.1
add 51272d9e7 Merge pull request #9200 from
apache/dependabot/maven/org.rocksdb-rocksdbjni-11.8.1
add 23b474ebd build(deps): bump com.github.luben:zstd-jni in /examples
add a3366c44d Merge pull request #9201 from
apache/dependabot/maven/examples/com.github.luben-zstd-jni-1.5.7-25
add bcb52604c 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 (93e2641f9)
\
N -- N -- N refs/heads/update-license-files (bcb52604c)
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 | 4 ++--
LICENSE-binary | 4 ++--
pom.xml | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)