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
discard e7fb2af4 Regen for commit f22ca1e7f2298eddcc59ae2a14ac08959c767973
add f7e540e3 Update antora-playbook.yml (#1337)
add 034a1918 Fix 4.11 is not a LTS
add a8a9aeae Regen for commit 034a19183d558a43dcc02a27d60c22d62259d5bb
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 (e7fb2af4)
\
N -- N -- N refs/heads/regen_bot (a8a9aeae)
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/release-4.11.0.md | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
