This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
discard 62a417cc0 Regen for commit 6a52e17fa9aa110aafbf750fee2db1250749a7ab
add 34433f5f6 Upgrade to Camel 4.23.0-SNAPSHOT (#3027)
add c3cd19f08 Regen for commit 34433f5f6c603faf027ae6198ad3033b1809b7c1
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 (62a417cc0)
\
N -- N -- N refs/heads/regen_bot (c3cd19f08)
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:
.../java/org/apache/camel/kamelets/catalog/KameletsCatalogTest.java | 2 +-
pom.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
