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-website.git
omit c6a0673a Regen for commit 499d5195b1e47d29709a0051d6a2267627d4a14c
add bf28c727 chore: camel k latest releases
add 1d2d2013 Regen for commit bf28c727f8ee8e4023966481364ac4bc25b9d7d0
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 (c6a0673a)
\
N -- N -- N refs/heads/regen_bot (1d2d2013)
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:
content/releases/k-runtime/release-2.16.0.md | 12 ++++++++++++
content/releases/k/release-2.0.0.md | 12 ++++++++++++
2 files changed, 24 insertions(+)
create mode 100644 content/releases/k-runtime/release-2.16.0.md
create mode 100644 content/releases/k/release-2.0.0.md
