This is an automated email from the ASF dual-hosted git repository.
gnodet 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 492ba8badd02 CAMEL-24228: Clarify upgrade guide is for migration only,
not new features
492ba8badd02 is described below
commit 492ba8badd021df9c605271b04ab6a52be76ed13
Author: Guillaume Nodet <[email protected]>
AuthorDate: Mon Jul 27 20:56:57 2026 +0200
CAMEL-24228: Clarify upgrade guide is for migration only, not new features
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
AGENTS.md | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/AGENTS.md b/AGENTS.md
index c3b78e3b4ae0..3c1844ec279c 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -136,11 +136,13 @@ When merging a PR, an agent MUST perform the following
steps **in order**:
- Every PR must include tests for new functionality or bug fixes.
- Every PR must include documentation updates where applicable.
- Any user-visible change must be documented in the upgrade guide
- (`docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_XX.adoc`) and
in the relevant
- command or component documentation page. This includes: changed defaults,
new auto-detection
- behavior, removed or renamed options, changed header names or values,
API/SPI signature changes,
- removed or deprecated components, migrated libraries, and renamed
documentation pages.
+ New features must be documented in the relevant command or component
documentation page.
+ Changes that affect existing users upgrading must also be documented in the
upgrade guide
+ (`docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_XX.adoc`).
This includes:
+ changed defaults, new auto-detection behavior, removed or renamed options,
changed header
+ names or values, API/SPI signature changes, removed or deprecated
components, migrated
+ libraries, and renamed documentation pages. The upgrade guide is for
migration only — do
+ NOT add new features to it.
For backported changes, the upgrade guide entry must be added on the `main`
branch (not on the
maintenance branch where the fix is backported).
- All code must pass formatting checks (`mvn formatter:format impsort:sort`)
before pushing.
