This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.google.cloud-google-cloud-storage-2.56.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 5143979a7c4 chore(deps): Bump com.google.cloud:google-cloud-storage
add 8ceb3eec8f2 chore(deps): Bump aws-java-sdk2-version from 2.32.29 to
2.32.30 (#19007)
add 28d2eec3a9a chore(deps): Bump io.camunda:zeebe-client-java from 8.7.10
to 8.7.11 (#19008)
add 4c58714cd41 chore(deps): Bump
org.citrusframework:citrus-jbang-connector (#19005)
add 3008ee5253f chore(deps): Bump com.google.cloud:google-cloud-storage
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 (5143979a7c4)
\
N -- N -- N
refs/heads/dependabot/maven/com.google.cloud-google-cloud-storage-2.56.0
(3008ee5253f)
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:
dsl/camel-jbang/camel-jbang-plugin-test/pom.xml | 2 +-
parent/pom.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
