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 eacb8895352 chore(deps): Bump org.springframework.amqp:spring-rabbit
add 093438d660b chore(deps): Bump aws-java-sdk2-version from 2.29.34 to
2.29.35 (#16582)
add 0601c0155fc chore(deps): Bump spring-security-version from 6.4.1 to
6.4.2 (#16583)
add 3ef8752b200 chore(deps): Bump
com.google.cloud:google-cloud-secretmanager-bom (#16584)
add 4b205920e7a chore(deps): Bump
com.google.cloud:google-cloud-functions-bom (#16586)
add 61ffd3a3ce5 chore(deps): Bump google-oauth-client-version from 1.36.0
to 1.37.0 (#16587)
add ba544e16e8b 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 (eacb8895352)
\
N -- N -- N
refs/heads/dependabot/maven/org.springframework.amqp-spring-rabbit-3.2.1
(ba544e16e8b)
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 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
