This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch CAMEL-20069
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 5c2c0a57498 CAMEL-20069 - Upgrade Azure SDK BOM to version 1.2.18
omit 990b3a126af Upgrade Flink to version 1.18.0
add 54f4a8ef442 Upgrade AWS SDK v2 to version 2.21.13 (#11883)
add 023466f13b2 Upgrade Flink to version 1.18.0 (#11884)
new 9f29434a51d CAMEL-20069 - Upgrade Azure SDK BOM to version 1.2.18
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 (5c2c0a57498)
\
N -- N -- N refs/heads/CAMEL-20069 (9f29434a51d)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
parent/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
