This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch
dependabot/npm_and_yarn/antora-ui-camel/cipher-base-1.0.7
in repository https://gitbox.apache.org/repos/asf/camel-website.git
discard d65d11c6 chore(deps): bump cipher-base from 1.0.4 to 1.0.7 in
/antora-ui-camel
add 8c696e23 Added branch camel-kafka-connector-4.14.x to
antora-playbook.yml (#1395)
add 3e2a7c1e Create release-4.14.0.md (#1394)
add 691e18fb chore(deps): bump cipher-base from 1.0.4 to 1.0.7 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 (d65d11c6)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/antora-ui-camel/cipher-base-1.0.7 (691e18fb)
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-playbook-snippets/antora-playbook.yml | 1 +
content/releases/ckc/release-4.14.0.md | 13 +++++++++++++
2 files changed, 14 insertions(+)
create mode 100644 content/releases/ckc/release-4.14.0.md