This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard fa306b6d3a Upgrade Quarkus to 3.12.0.CR1
add 760152d5a5 Regen SBOM from commit
e46046465c80bbea8878cf3ee4b99a01f97a2a60 (#6105)
add c86e750782 Use a consistent release version for CompilationProvider
add c530f19242 Upgrade jolokia to 2.0.2
add 5df03317ad --- updated-dependencies: - dependency-name:
org.codehaus.mojo:build-helper-maven-plugin dependency-type:
direct:production update-type: version-update:semver-minor ...
new 8ee2a5748f Upgrade Quarkus to 3.12.0.CR1
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 (fa306b6d3a)
\
N -- N -- N refs/heads/quarkus-main (8ee2a5748f)
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 1 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 | 15305 ++++++++++---------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 14785 +++++++++---------
.../quarkus/core/deployment/util/CamelSupport.java | 1 +
.../csimple/deployment/CSimpleProcessor.java | 5 +-
.../dsl/jsh/deployment/JshDslProcessor.java | 3 +-
pom.xml | 4 +-
poms/bom/pom.xml | 5 +-
poms/bom/src/main/generated/flattened-full-pom.xml | 7 +-
8 files changed, 15163 insertions(+), 14952 deletions(-)
