This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/elasticsearch-java-client-version-9.2.4
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 02461785f20e chore(deps): Bump elasticsearch-java-client-version from
9.2.3 to 9.2.4
add 5fd6a891a933 chore(deps): Bump aws-java-sdk2-version from 2.41.6 to
2.41.7 (#20802)
add 36c1070b2efa chore(deps): Bump undertow-version from 2.3.20.Final to
2.3.21.Final (#20803)
add 410ff928057e chore(ci): run alternative os check nightly (#20801)
add e4256fa4e9dd chore(deps-dev): Bump io.projectreactor:reactor-core from
3.8.1 to 3.8.2 (#20804)
add f87e1902b6a3 chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer (#20805)
add 29858de96775 chore(deps): Bump com.pubnub:pubnub-gson from 12.0.4 to
12.1.1 (#20806)
add 58703166c9f5 chore(deps): Bump elasticsearch-java-client-version from
9.2.3 to 9.2.4
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 (02461785f20e)
\
N -- N -- N
refs/heads/dependabot/maven/elasticsearch-java-client-version-9.2.4
(58703166c9f5)
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:
.github/workflows/alternative-os-build-main.yml | 6 ++----
parent/pom.xml | 10 +++++-----
2 files changed, 7 insertions(+), 9 deletions(-)
