This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.plexus-plexus-sec-dispatcher-3.0.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 46bd602c590 chore(deps): Bump org.codehaus.plexus:plexus-sec-dispatcher
add cf9404e5e79 CAMEL-22156: camel-management: Fix some tests running on
windows
add 08f2b8e2246 chore(deps): Bump aws-java-sdk2-version from 2.31.60 to
2.31.61 (#18336)
add bf34574c218 chore(deps): Bump com.github.mwiede:jsch from 2.27.0 to
2.27.2 (#18338)
add d3b0f43fac7 chore(deps): Bump io.projectreactor.netty:reactor-netty
(#18339)
add 873ea0c1821 chore(deps): Bump org.codehaus.plexus:plexus-cipher from
2.0 to 2.1.0 (#18337)
add be1c2b29c9e chore(deps): Bump org.codehaus.plexus:plexus-sec-dispatcher
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 (46bd602c590)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-sec-dispatcher-3.0.0
(be1c2b29c9e)
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:
.../ManagedBrowsableEndpointAsJSonFileTest.java | 16 ++++++++++++++--
.../ManagedBrowsableEndpointAsXmlFileTest.java | 16 ++++++++++++++--
dsl/camel-jbang/camel-launcher/pom.xml | 2 +-
parent/pom.xml | 6 +++---
4 files changed, 32 insertions(+), 8 deletions(-)
