This is an automated email from the ASF dual-hosted git repository. acosentino pushed a change to branch kafka-apicurio-json in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
discard cc36e365 Added Kafka Apicurio Registry Kamelet supporting Json Schema add ad2c52dd Bump com.amazon.redshift:redshift-jdbc42 from 2.1.0.27 to 2.1.0.28 (#2043) add 1d4d09b1 Regen for commit ad2c52dd92239262c48d5566fb328bcf004d23ea (#2045) add 28312f4e Added Kafka Apicurio Registry Kamelet supporting Json Schema add 6e49b4c8 Added Kafka Apicurio Registry Kamelet supporting Json Schema add c275bf95 Added Kafka Apicurio Registry Kamelet supporting Json Schema add 6209a68a Added Kafka Apicurio Registry Kamelet supporting Json Schema add 6dfa07dc Added Kafka Apicurio Registry Kamelet supporting Json Schema 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 (cc36e365) \ N -- N -- N refs/heads/kafka-apicurio-json (6dfa07dc) 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: docs/modules/ROOT/nav.adoc | 1 + kamelets/aws-redshift-sink.kamelet.yaml | 2 +- kamelets/aws-redshift-source.kamelet.yaml | 2 +- kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml | 4 ++-- .../src/main/resources/kamelets/aws-redshift-sink.kamelet.yaml | 2 +- .../src/main/resources/kamelets/aws-redshift-source.kamelet.yaml | 2 +- .../kafka-not-secured-apicurio-registry-json-source.kamelet.yaml | 4 ++-- pom.xml | 2 +- 8 files changed, 10 insertions(+), 9 deletions(-)