This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 3ec2d2c8ad7b 4.14 is EOL
3ec2d2c8ad7b is described below

commit 3ec2d2c8ad7bd63f6619fc71e05e0766c1f00143
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Aug 12 07:44:11 2026 +0200

    4.14 is EOL
---
 .asf.yaml                                  | 2 +-
 .github/CI-ARCHITECTURE.md                 | 2 +-
 .github/actions/labeler/label-config.yml   | 1 +
 .oss-ai-helper-rules/project-guidelines.md | 2 +-
 design/headers.adoc                        | 2 +-
 5 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/.asf.yaml b/.asf.yaml
index 3fcd461f9591..f0c92fdc2407 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -47,8 +47,8 @@ github:
 
   protected_branches:
     main: {}
-    camel-4.14.x: {}
     camel-4.18.x: {}
+    camel-4.22.x: {}
   
 notifications:
   pullrequests: [email protected]
diff --git a/.github/CI-ARCHITECTURE.md b/.github/CI-ARCHITECTURE.md
index 2e77007d1ad1..90139a08698b 100644
--- a/.github/CI-ARCHITECTURE.md
+++ b/.github/CI-ARCHITECTURE.md
@@ -63,7 +63,7 @@ PR comment: /component-test kafka http
 
 ### `main-build.yml` — Main branch build
 
-- **Trigger**: `push` to main, camel-4.14.x, camel-4.18.x
+- **Trigger**: `push` to main, camel-4.18.x, camel-4.22.x
 - **Steps**: Same as PR build but without comment posting
 
 ### `sonar-build.yml` + `sonar-scan.yml` — SonarCloud PR analysis
diff --git a/.github/actions/labeler/label-config.yml 
b/.github/actions/labeler/label-config.yml
index 3fcfabd606f7..baeddb005580 100644
--- a/.github/actions/labeler/label-config.yml
+++ b/.github/actions/labeler/label-config.yml
@@ -26,6 +26,7 @@ lts:
       - 'camel-4.10.x'
       - 'camel-4.14.x'
       - 'camel-4.18.x'
+      - 'camel-4.22.x'
 
 ci:
   - changed-files:
diff --git a/.oss-ai-helper-rules/project-guidelines.md 
b/.oss-ai-helper-rules/project-guidelines.md
index 83116b921521..b555347b58ef 100644
--- a/.oss-ai-helper-rules/project-guidelines.md
+++ b/.oss-ai-helper-rules/project-guidelines.md
@@ -11,7 +11,7 @@ This rule file contains branching, commit, PR, and 
task-finding conventions for
 - **CI-issue branch:** `ci-issue/<short-slug>`
 - **Commit format (ci-issue):** `ci: <brief description>`
 - **PR creation:** always
-- **Backport upgrade-guide policy:** the 
`docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_XX.adoc` files 
for ALL versions live on `main` and act as the canonical history across all 
releases. When a PR is backported to a maintenance branch (e.g. `camel-4.18.x`, 
`camel-4.14.x`) and adds an upgrade-guide note for that release line, the 
corresponding entry must ALSO be added to the matching 
`camel-4x-upgrade-guide-4_XX.adoc` file on `main` — either as part of the 
backport workfl [...]
+- **Backport upgrade-guide policy:** the 
`docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_XX.adoc` files 
for ALL versions live on `main` and act as the canonical history across all 
releases. When a PR is backported to a maintenance branch (e.g. `camel-4.22.x`, 
`camel-4.18.x`) and adds an upgrade-guide note for that release line, the 
corresponding entry must ALSO be added to the matching 
`camel-4x-upgrade-guide-4_XX.adoc` file on `main` — either as part of the 
backport workfl [...]
 - **Find-task source:** Jira
 - **Find-task beginner JQL:** `project = CAMEL AND status = Open AND labels = 
good-first-issue` (maxResults=10)
 - **Find-task intermediate:** Filter 12352792 (easy issues)
diff --git a/design/headers.adoc b/design/headers.adoc
index 660355d2eef9..686564afbd8c 100644
--- a/design/headers.adoc
+++ b/design/headers.adoc
@@ -202,7 +202,7 @@ migration. The upgrade guide is the primary migration aid.
 === Backport policy
 
 When a header rename is backported to a maintenance branch (e.g.,
-`camel-4.18.x`, `camel-4.14.x`):
+`camel-4.22.x`, `camel-4.18.x`):
 
 * Add an upgrade guide entry on the maintenance branch.
 * Also add the corresponding entry on `main` to keep the version-specific

Reply via email to