This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 43af4041165 Regen for commit 82b8cf1f28252bb7fc26bfd37df6219f3fd46b37
add 56c57a24d8d (chores) camel-hyperledger-aries: avoid risky unboxing
add 6ea355e1a8f (chores) camel-jdbc: avoid risky unboxing
add a41f266b97b (chores) camel-openapi-java: avoid risky unboxing
add ac426faea2f (chores) camel-pg-replication-slot: avoid risky unboxing
add f176c4c1591 (chores) camel-resteasy: avoid risky unboxing
add 89616a38dd5 (chores) camel-cxf: avoid risky unboxing
add 7ad50e3fc02 Regen for commit 89616a38dd5a67a8728365e0368bf2a558adea1a
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 (43af4041165)
\
N -- N -- N refs/heads/regen_bot (7ad50e3fc02)
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:
.../component/cxf/jaxws/DefaultCxfBinding.java | 2 +-
.../CredentialDefinitionsServiceHandler.java | 22 ++++++++++++----------
.../apache/camel/component/jdbc/JdbcProducer.java | 10 +++++-----
.../camel/openapi/OpenApiRestProducerFactory.java | 2 +-
.../slot/PgReplicationSlotConsumer.java | 2 +-
.../resteasy/servlet/ResteasyCamelServlet.java | 2 +-
6 files changed, 21 insertions(+), 19 deletions(-)