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 7c1e97a2b Regenerate license files after dependency changes
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)
add 469505f6b build(deps): bump jetty.version from 12.1.12 to 12.1.13 in
/examples (#9127)
add 6a53a2dc6 build(deps): bump org.apache.commons:commons-lang3 in
/examples (#9128)
add cf714c1d9 build(deps-dev): bump
org.apache.maven.plugins:maven-surefire-report-plugin (#9130)
add fe67e8e4c build(deps): bump org.codehaus.mojo:exec-maven-plugin in
/examples (#9133)
add 9a81e0fc5 build(deps): bump bouncycastle.version from 1.85 to 1.86 in
/examples (#9135)
add a5a387392 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 (7c1e97a2b)
\
N -- N -- N refs/heads/update-license-files (a5a387392)
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 | 2 +-
LICENSE-binary | 2 +-
pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
