This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.springframework.amqp-spring-rabbit-3.2.1
in repository https://gitbox.apache.org/repos/asf/camel.git
omit ba544e16e8b chore(deps): Bump org.springframework.amqp:spring-rabbit
add 8458e68adf2 chore(deps): Bump org.mnode.ical4j:ical4j from 4.0.6 to
4.0.7 (#16588)
add 97288d49c9a chore(deps): Bump junit-jupiter-version from 5.11.3 to
5.11.4 (#16589)
add d97209a1c09 chore(deps): Bump com.pubnub:pubnub-gson from 10.3.1 to
10.3.2 (#16590)
add 97a107ea741 chore(deps-dev): Bump com.google.guava:guava (#16585)
add 85b357e584d chore(deps): Bump org.springframework.amqp:spring-rabbit
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 (ba544e16e8b)
\
N -- N -- N
refs/heads/dependabot/maven/org.springframework.amqp-spring-rabbit-3.2.1
(85b357e584d)
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:
parent/pom.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
