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 4ae38b0eea Add workaround for RemoteCacheManager bean discovery #4841
discard d79e133710 Revert "Revert "Restore smallrye-reactive-messaging-camel
extension""
discard d20bcafeb1 Upgrade Quarkus to 3.1.0.CR1
add 3909cddc36 Updated CHANGELOG.md
add 64bf8943e3 Regen SBOM from commit
3909cddc3607838ed39876638dbd3ab2697d7350
add 70bcff9e81 Updated CHANGELOG.md
new 23349e040d Upgrade Quarkus to 3.1.0.CR1
new b132711b38 Revert "Revert "Restore smallrye-reactive-messaging-camel
extension""
new d4878b7b0b Add workaround for RemoteCacheManager bean discovery #4841
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 (4ae38b0eea)
\
N -- N -- N refs/heads/quarkus-main (d4878b7b0b)
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 3 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 | 2 +
camel-quarkus-sbom/camel-quarkus-sbom.json | 19546 +++++++++++++--------------
camel-quarkus-sbom/camel-quarkus-sbom.xml | 8778 ++++++------
3 files changed, 14162 insertions(+), 14164 deletions(-)
