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 7ab9d7b46 Regenerate license files after dependency changes
omit e48e5bf44 Merge pull request #9222 from
apache/dependabot/maven/examples/byte-buddy.version-1.18.16
omit 8672b53f2 Merge pull request #9219 from
apache/dependabot/maven/spring.version-7.0.10
omit c3f16c45b Merge pull request #9218 from
apache/dependabot/maven/examples/surefire.version-3.6.1
omit e1e182779 Merge pull request #9217 from
apache/dependabot/maven/examples/org.rocksdb-rocksdbjni-11.8.1
omit 94b14ae7f build(deps): bump byte-buddy.version in /examples
omit 659ed395f build(deps): bump spring.version from 7.0.9 to 7.0.10
omit 01dd4f25a build(deps): bump surefire.version from 3.6.0 to 3.6.1 in
/examples
omit 1b4c0353d build(deps): bump org.rocksdb:rocksdbjni in /examples
new 352169787 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 (7ab9d7b46)
\
N -- N -- N refs/heads/update-license-files (352169787)
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:
pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)