This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
discard 44faf90 Dependency parity validator workarounds
discard 09cb6f0 Remove Deployment BOM
discard a053ffa Temporarily disable debezium tests until #1311 and
associtated issues are fixed
discard 161f236 Upgrade to Quarkus 1.6.0 - WIP
add 4aab307 Make the local Antora build produce .htaccess file with
redirects based on :page-aliases: attributes in the AsciiDoc pages the content
of that file can by copied to
https://github.com/apache/camel-website/blob/master/static/.htaccess
new b27a919 Upgrade to Quarkus 1.6.0 - WIP
new e600901 Temporarily disable debezium tests until #1311 and
associtated issues are fixed
new bc894a1 Remove Deployment BOM
new 0eed3af Dependency parity validator workarounds
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 (44faf90)
\
N -- N -- N refs/heads/quarkus-master (0eed3af)
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:
docs/antora-playbook.yml | 2 +
docs/package.json | 9 +-
docs/yarn.lock | 1739 ++++++++++++++--------------------------------
3 files changed, 527 insertions(+), 1223 deletions(-)
