This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot_sbom
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
omit a49054e2aa Regen SBOM from commit
82a326a6c1770c2e31f9d5c88df707ec60132c0e
add 3355b48725 Regen SBOM from commit
82a326a6c1770c2e31f9d5c88df707ec60132c0e (#6275)
add 3c85c2e7ee Disabled jdbc/db2 test for native in FIPS (#6272)
add 46d62bc3cb Bump quarkiverse-langchain4j.version from 0.16.2 to 0.16.4
add 7163fc694f Auto generated changes for dependabot commit
309e723fec9adfd9adb26f4ace1f9013696b2d68
add ba9f0d0fcf Revert "Auto generated changes for dependabot commit
309e723fec9adfd9… (#6277)
add 491403082b Downgrade quarkus-langchain4j to 0.16.2 to workaround issue
#6278
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 (a49054e2aa)
\
N -- N -- N refs/heads/regen_bot_sbom (491403082b)
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:
.../org/apache/camel/quarkus/component/jdbc/db2/CamelDb2JdbcIT.java | 2 ++
1 file changed, 2 insertions(+)
