This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch blog/camel-tui-editor
in repository https://gitbox.apache.org/repos/asf/camel-website.git
omit d3b6cb87 blog: Position editor as prototyping tool, update date,
remove TamboUI note
omit 5a021b7c blog: Replace and resize TUI editor screenshots to 1600px
omit 1656f304 blog: Add Go to route feature to TUI editor blog post
omit 2f64a118 blog: Add note about AI-captured screenshots and TamboUI
alignment bug
omit 15e70ac1 blog: Add TUI editor screenshots to follow-up blog post
omit e9d424f6 blog: Draft Camel TUI editor follow-up blog post
omit 52f8b940 blog: Add TUI screenshot to 4.22 what's new blog post
omit 9fd9946c blog: Add Camel Spring Boot section and refine AI section
omit bb22557c blog: Add Apache Camel 4.22 LTS what's new blog post
add 527abb19 fix: netlify config preview update
add 7a7e24e0 chore(deps): bump socket.io-parser from 4.2.4 to 4.2.7 (#1715)
add 7466bed9 chore(deps): bump fast-uri from 3.1.4 to 3.1.5 (#1717)
add 0259dfbb docs(website): add "Secure out of the box" section to Trust
page (#1680) (#1706)
add d7d87e8a chore(deps-dev): bump js-yaml from 4.3.0 to 4.3.1
add 52a9c898 chore(deps): dedupe for js-yaml-4.3.1
add 7c534e11 fix: strip workspaces before netlify deploy to bypass
monorepo detection
add 727deee9 fix: add --no-build to netlify deploy to skip unwanted build
add d3d97948 Updated
add 644bd711 docs(tooling): promote Camel TUI to its own section with
screenshot and editor details
add 8d357009 blog: Draft Camel TUI editor follow-up blog post
add 4a3775dc blog: Add TUI editor screenshots to follow-up blog post
add c8566dea blog: Add note about AI-captured screenshots and TamboUI
alignment bug
add b668eabc blog: Add Go to route feature to TUI editor blog post
add d1a659b1 blog: Replace and resize TUI editor screenshots to 1600px
add 6b38f207 blog: Position editor as prototyping tool, update date,
remove TamboUI note
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 (d3b6cb87)
\
N -- N -- N refs/heads/blog/camel-tui-editor (6b38f207)
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:
.github/workflows/preview.yaml | 3 +-
antora-ui-camel/package.json | 4 +-
content/blog/2026/08/camel422-whatsnew/index.md | 384 ---------------------
content/community/user-stories.md | 1 +
content/security/_index.md | 7 +
content/tooling/_index.md | 8 +-
.../camel-tui-overview.png | Bin
content/trust/_index.md | 36 ++
package.json | 4 +-
yarn.lock | 28 +-
10 files changed, 71 insertions(+), 404 deletions(-)
delete mode 100644 content/blog/2026/08/camel422-whatsnew/index.md
rename content/{blog/2026/08/camel422-whatsnew =>
tooling}/camel-tui-overview.png (100%)
