This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/quarkiverse-fory.version-1.3.0
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard f16882457d Auto generated changes for dependabot commit
6c01a2196fa2c9c0072dee7170cc136780bee159
discard 6c01a2196f Bump quarkiverse-fory.version from 0.5.0 to 1.3.0
add e7ad1c8388 Regen SBOM from commit
e999b99e6c00e29b3b87975b1035b01b498c4336 (#8800)
add 43bf273b7f Fix incremental build not testing Dependabot PRs
add a146dd2c37 Adjust Scalpel full build triggers for ci-build workflow
add a16dfd09cb Clone Quarkus from the 3.x branch
add cf9209f1d7 Bump quarkiverse-fory.version from 0.5.0 to 1.3.0
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 (f16882457d)
\
N -- N -- N
refs/heads/dependabot/maven/quarkiverse-fory.version-1.3.0 (cf9209f1d7)
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:
.github/workflows/ci-build.yaml | 6 +-
.github/workflows/quarkus-master-cron.yaml | 2 +-
camel-quarkus-sbom/camel-quarkus-sbom.json | 764 +++++++++++++--------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 523 +++++++++-----
poms/bom/src/main/generated/flattened-full-pom.xml | 4 +-
.../src/main/generated/flattened-reduced-pom.xml | 4 +-
.../generated/flattened-reduced-verbose-pom.xml | 4 +-
.../camel/quarkus/maven/IncrementalBuildMojo.java | 22 +-
8 files changed, 858 insertions(+), 471 deletions(-)
