This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch camel-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard c03848b BigQuery native support
omit 673bae5 Google PubSub native support
omit ed7cae5 [Camel 3.7] JSON-B data format support
omit d2fa7e2 Upgrade to Camel 3.7.0
add 1e834dd Updated CHANGELOG.md
add 95e13ee Fix persistence of WireMock mappings
add 4682c75 Fixup 9217ba9 Solr native support fixes #1703
add 7d1573f Added a bug trap to catch more info in the context #1978
new a6ab6e6 Upgrade to Camel 3.7.0
new b0348dc [Camel 3.7] JSON-B data format support
new b00b6d6 Google PubSub native support
new 1b2d5e3 BigQuery native support
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 (c03848b)
\
N -- N -- N refs/heads/camel-master (1b2d5e3)
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 4 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:
CHANGELOG.md | 7 +++++--
.../test/wiremock/WireMockTestResourceLifecycleManager.java | 10 +++++++---
.../camel/quarkus/component/nats/it/NatsTestResource.java | 6 +++++-
integration-tests/solr/pom.xml | 2 +-
4 files changed, 18 insertions(+), 7 deletions(-)
