This is an automated email from the ASF dual-hosted git repository.
ppalaga pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard 31d229c999 Upgrade Quarkus to 3.17.0.CR1
add e2a38e25c6 langchain4j: fix link to camel core parameter binding usage
add fea7adeea3 Fix Camel header documentation
add c22a9e566f Regen SBOM from commit
fea7adeea382afd3e86d8fcf54c9308139f5ab2c (#6665)
new 797766653c Upgrade Quarkus to 3.17.0.CR1
new 4a39502c05 UpdateExtensionDocPageMojo is broken, fix #6418
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 (31d229c999)
\
N -- N -- N refs/heads/quarkus-main (4a39502c05)
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 2 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:
camel-quarkus-sbom/camel-quarkus-sbom.json | 19726 +++++++++----------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 18999 +++++++++---------
.../ROOT/examples/js/{quarkus.js => camel.js} | 29 +-
.../pages/reference/extensions/langchain4j.adoc | 2 +-
.../ROOT/partials/component-endpoint-headers.adoc | 2 +-
.../runtime/src/main/doc/configuration.adoc | 2 +-
.../quarkus/maven/UpdateExtensionDocPageMojo.java | 28 +-
7 files changed, 19143 insertions(+), 19645 deletions(-)
copy docs/modules/ROOT/examples/js/{quarkus.js => camel.js} (54%)
