This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/antora-ui-camel/hono-4.12.12
in repository https://gitbox.apache.org/repos/asf/camel-website.git
discard f24b8424 chore(deps): bump hono from 4.12.2 to 4.12.12 in
/antora-ui-camel
add 73975fa6 Move schema to correct folder
add 87efef62 chore(deps): bump @hono/node-server in /antora-ui-camel
add c82b4e3d chore(deps): bump hono from 4.12.2 to 4.12.12 in
/antora-ui-camel
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 (f24b8424)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/antora-ui-camel/hono-4.12.12 (c82b4e3d)
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:
antora-ui-camel/yarn.lock | 6 +++---
.../camel-spring-xml-4.18.1.xsd => spring/camel-spring-4.18.1.xsd} | 0
2 files changed, 3 insertions(+), 3 deletions(-)
rename static/schema/{spring-xml/camel-spring-xml-4.18.1.xsd =>
spring/camel-spring-4.18.1.xsd} (100%)
