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 af5951f36 Regenerate license files after dependency changes
add 659ed395f build(deps): bump spring.version from 7.0.9 to 7.0.10
add 8672b53f2 Merge pull request #9219 from
apache/dependabot/maven/spring.version-7.0.10
add 94b14ae7f build(deps): bump byte-buddy.version in /examples
add e48e5bf44 Merge pull request #9222 from
apache/dependabot/maven/examples/byte-buddy.version-1.18.16
add a085d3c3e build(deps): bump com.esotericsoftware:kryo from 5.6.2 to
5.7.1
add ececed8ee Merge pull request #9223 from
apache/dependabot/maven/com.esotericsoftware-kryo-5.7.1
add 1c6a604d1 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 (af5951f36)
\
N -- N -- N refs/heads/update-license-files (1c6a604d1)
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 | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)