This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/aws-java-sdk2-version-2.44.8
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 12613e682be6 chore(deps): Bump aws-java-sdk2-version from 2.44.6 to
2.44.8
add cdc653298383 CAMEL-23516: docs - sync camel-xmpp 4.14 upgrade-guide
entry to main
add a1f57e60041b Fix main branch by reverting requirements on message for
log to not be null
add 907dc0cb3bef Fix main branch ResumeStrategyConfiguration - revert
requirements for non null resume cache
add 08df8bdc7bba CAMEL-23528: document camel-neo4j property name
validation in the 4.14 upgrade guide (#23324)
add 4b45e4bf0d9f CAMEL-23532: docs - sync camel-vertx-websocket /
camel-atmosphere-websocket / camel-iggy 4.18 upgrade-guide entry to main
(#23315)
add f8e97eb9ade1 chore(deps): Bump aws-java-sdk2-version from 2.44.6 to
2.44.8
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 (12613e682be6)
\
N -- N -- N
refs/heads/dependabot/maven/aws-java-sdk2-version-2.44.8 (f8e97eb9ade1)
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:
.../camel/resume/ResumeStrategyConfiguration.java | 4 +--
.../java/org/apache/camel/spi/CamelLogger.java | 27 +++++++-------------
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 19 ++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 29 ++++++++++++++++++++++
4 files changed, 59 insertions(+), 20 deletions(-)
