This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 4cbc1c024b2 chore(deps): Bump com.google.cloud:google-cloud-bigquery
(#17291)
omit 177248f792e chore(deps): Bump com.google.cloud:google-cloud-pubsublite
(#17290)
omit 841d937dc05 chore(deps): Bump google-auth-library-oauth2-http-version
(#17289)
omit 7132c30a9a2 chore(deps): Bump com.google.cloud:google-cloud-storage
(#17288)
omit 8a8a8d45f99 chore(deps): Bump aws-java-sdk2-version from 2.30.28 to
2.30.29 (#17286)
omit 20025017eef Flaky test
omit e0f6274385f camel-jbang: upgrade SB and Q
omit 5de9637ba08 Update known releases in catalog
omit e5251996e0e CAMEL-21760: OpenID Connect & OAuth for Camel Kafka, Web,
Rest (#17196)
omit 08d6a41417f feat(components): Camel Opentemeletry 2
omit a1acf35bc5e Add proxyHost, proxyPort, and tls options to
camel-pinecone (#17284)
omit f2939135338 CAMEL-20837: minor api adjustments (#17285)
omit 6b1e9c66ac1 CAMEL-21805 - Camel-IBM-Secrets-manager: Add ListSecrets
operation (#17283)
new e862ead9080 CAMEL-21805 - Camel-IBM-Secrets-manager: Add ListSecrets
operation (#17283)
new eeafa1a66dc CAMEL-20837: minor api adjustments (#17285)
new 51ad70ff904 Add proxyHost, proxyPort, and tls options to
camel-pinecone (#17284)
new 93201884613 feat(components): Camel Opentemeletry 2
new 2f241970157 CAMEL-21760: OpenID Connect & OAuth for Camel Kafka, Web,
Rest (#17196)
new c86d57e812e Update known releases in catalog
new 3ac02912d1d camel-jbang: upgrade SB and Q
new 8fd5116daf8 Flaky test
new ad224bb9177 chore(deps): Bump aws-java-sdk2-version from 2.30.28 to
2.30.29 (#17286)
new 249c58330c6 chore(deps): Bump com.google.cloud:google-cloud-storage
(#17288)
new 310626ff5ef chore(deps): Bump google-auth-library-oauth2-http-version
(#17289)
new 159315b226e chore(deps): Bump com.google.cloud:google-cloud-pubsublite
(#17290)
new babdec0c7b9 chore(deps): Bump com.google.cloud:google-cloud-bigquery
(#17291)
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 (4cbc1c024b2)
\
N -- N -- N refs/heads/main (babdec0c7b9)
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 13 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:
