This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/2.x/jakarta-activation-version-2.0.1
in repository https://gitbox.apache.org/repos/asf/storm.git
discard 01e90624a Bump jakarta-activation-version from 1.2.1 to 2.0.1
add 30ca0be6e Bump org.apache.thrift:libthrift from 0.22.0 to 0.23.0
(#8686)
add 2e50d45e1 Regenerate license files after dependency changes (#8689)
add 0ee35cd7f Bump org.apache.maven:maven-resolver-provider from 3.9.15 to
3.9.16 (#8670)
add 68e5c2b82 Bump org.apache.logging.log4j:log4j-bom from 2.25.4 to
2.26.0 (#8685)
add 6baa3abb3 Bump org.apache.commons:commons-configuration2 from 2.14.0
to 2.15.0 (#8684)
add 15acc641e Bump jakarta.ws.rs:jakarta.ws.rs-api from 3.1.0 to 4.0.0
(#8682)
add 0eef78f60 Bump io.netty:netty-bom from 4.2.12.Final to 4.2.13.Final
(#8675)
add 31ef85186 build(deps): bump jakarta-activation-version from 1.2.1 to
2.0.1
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 (01e90624a)
\
N -- N -- N
refs/heads/dependabot/maven/2.x/jakarta-activation-version-2.0.1 (31ef85186)
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 | 12 ++++++------
3 files changed, 8 insertions(+), 8 deletions(-)
