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 d74a11a78 Regenerate license files after dependency changes
add 9ba41d635 Bump com.github.luben:zstd-jni from 1.5.7-8 to 1.5.7-9 in
/examples
add 605a24aa3 Merge pull request #8739 from
apache/dependabot/maven/examples/com.github.luben-zstd-jni-1.5.7-9
add f64ef4fcd Bump org.junit:junit-bom from 6.0.3 to 6.1.0 in /examples
add 694941a30 Merge pull request #8737 from
apache/dependabot/maven/examples/org.junit-junit-bom-6.1.0
add 3731bf4bf Bump org.ow2.asm:asm from 9.10 to 9.10.1 in /examples
add 4d921784d Merge pull request #8736 from
apache/dependabot/maven/examples/org.ow2.asm-asm-9.10.1
add 813eef866 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 (d74a11a78)
\
N -- N -- N refs/heads/update-license-files (813eef866)
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 | 6 +++---
3 files changed, 7 insertions(+), 7 deletions(-)
