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 95dcd0350 Regenerate license files after dependency changes
add b04ba6749 build(deps): bump zookeeper.version from 3.9.5 to 3.9.6 in
/examples (#9120)
add 984ac70ef build(deps-dev): bump org.codehaus.mojo:taglist-maven-plugin
(#9122)
add 868a8b69d build(deps): bump byte-buddy.version in /examples (#9123)
add 6c35aea3f build(deps): bump slf4j.version from 2.0.18 to 2.0.20 in
/examples (#9124)
add d3e354e3e build(deps): bump com.github.ben-manes.caffeine:caffeine in
/examples (#9125)
add cdde17714 build(deps-dev): bump
io.github.git-commit-id:git-commit-id-maven-plugin (#9126)
new 8710f06fd 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 (95dcd0350)
\
N -- N -- N refs/heads/update-license-files (8710f06fd)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
DEPENDENCY-LICENSES | 2 +-
LICENSE-binary | 2 +-
pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
