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 f6ed17769 Regenerate license files after dependency changes
add ef486caeb build(deps): bump commons-logging:commons-logging from 1.3.6
to 1.4.0 (#8825)
add 01c47351c build(deps): bump org.junit:junit-bom from 6.1.0 to 6.1.1
(#8826)
add 472ebbbcd build(deps): bump org.apache.hbase:hbase-client (#8828)
add b6deab7b6 build(deps): bump byte-buddy.version from 1.18.8 to 1.18.10
(#8829)
add b31401431 build(deps-dev): bump
com.github.eirslett:frontend-maven-plugin (#8830)
add fdd551514 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 (f6ed17769)
\
N -- N -- N refs/heads/update-license-files (fdd551514)
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 | 20 ++++++++++----------
LICENSE-binary | 20 ++++++++++----------
pom.xml | 4 ++--
storm-webapp/pom.xml | 2 +-
4 files changed, 23 insertions(+), 23 deletions(-)
