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 1e2cf05f0 Regenerate license files after dependency changes
add 9b2c141df build(deps): bump jakarta.ws.rs:jakarta.ws.rs-api from 3.1.0
to 4.0.0
add f1176ff52 Merge pull request #8926 from
apache/dependabot/maven/jakarta.ws.rs-jakarta.ws.rs-api-4.0.0
add 1f436ead0 build(deps): bump org.apache.logging.log4j:log4j-bom in
/examples
add bc1dd66b4 Merge pull request #8929 from
apache/dependabot/maven/examples/org.apache.logging.log4j-log4j-bom-2.26.1
add 95143a1bb 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 (1e2cf05f0)
\
N -- N -- N refs/heads/update-license-files (95143a1bb)
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(-)
