This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/io.nats-jnats-2.25.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard e0a18465198a chore(deps): Bump io.nats:jnats from 2.24.1 to 2.25.0
add f45e3c08ab87 chore(camel-test-infra-infinispan): upgrade
infinispan.container to 16.1 (#20744)
add 170017e50ff7 chore(deps): Bump aws-java-sdk2-version from 2.41.5 to
2.41.6 (#20785)
add 2fcab7684e3f chore: add gpg key for pcongiusti
add 643f19b8c4ef chore(deps): Bump com.cedarsoftware:java-util from 4.80.0
to 4.81.0 (#20786)
add d7e37d885220 chore(deps): Bump io.nats:jnats from 2.24.1 to 2.25.0
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 (e0a18465198a)
\
N -- N -- N refs/heads/dependabot/maven/io.nats-jnats-2.25.0
(d7e37d885220)
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:
KEYS | 57 ++++++++++++++++++++++
parent/pom.xml | 4 +-
.../infra/infinispan/services/container.properties | 2 +-
3 files changed, 60 insertions(+), 3 deletions(-)
