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 8ba49ddb Regen for commit 53343b527d05c4066c7e0419e7704cc42a097359 add d5498b29 Add release notes and blog entry for Camel 3.21.2 add 16d8f07c Regen for commit d5498b29e94e6db0ad73d4494898fb67b8f5f2da 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 (8ba49ddb) \ N -- N -- N refs/heads/regen_bot (16d8f07c) 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: .../10/RELEASE-3.21.2}/featured.jpeg | Bin .../{09/RELEASE-3.21.1 => 10/RELEASE-3.21.2}/index.md | 10 +++++----- content/releases/release-3.21.2.md | 17 +++++++++++++++++ 3 files changed, 22 insertions(+), 5 deletions(-) copy content/blog/{2021/05/RELEASE-3.10.0 => 2023/10/RELEASE-3.21.2}/featured.jpeg (100%) copy content/blog/2023/{09/RELEASE-3.21.1 => 10/RELEASE-3.21.2}/index.md (67%) create mode 100644 content/releases/release-3.21.2.md