davsclaus opened a new pull request, #26333: URL: https://github.com/apache/camel/pull/26333
## What Adds five upgrade-guide entries to `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc` on `main`, copied verbatim from the same file on `camel-4.22.x`. ## Why The version-specific upgrade guides on `main` are the canonical history across all release lines (see `CLAUDE.md`, "Backport upgrade-guide policy"). When a PR is backported to a maintenance branch and adds an upgrade-guide note there, the matching entry must also land in `main`'s copy of that file. That did not happen for five backports, so `main`'s 4.22 guide is missing notes that are actually shipping in 4.22.x. Each of them exists on `main` only in the **4.23** guide, which is not where a user upgrading to a 4.22.x patch release would look. This was noticed while merging #26320, whose conflict resolution moved the note from the 4.23 guide into the 4.22 guide on the maintenance branch; the sweep for the same drift turned up four more. ## Entries added | Entry | Backport | |---|---| | `camel-support` — `BackgroundTask.schedule` cancels its repeating schedule | | | `camel-master` — `backOffMaxAttempts` bounds the delegate start attempts | | | `camel-servlet`, `camel-jetty` — `fileNameExtWhitelist` enforced against the submitted file name | #26320 | | `camel-tensorflow-serving` — the `Target` and `Credentials` headers are deprecated | | | `camel-hazelcast` — `ReplicatedHazelcastAggregationRepository` applies the default serialization filter | | After this change, the set of `===` sections in `camel-4x-upgrade-guide-4_22.adoc` is identical on `main` and `camel-4.22.x` (the two files still order them differently, which is pre-existing). ## Notes Documentation only — no code, no generated files, nothing to regenerate. The text is copied unchanged from `camel-4.22.x` rather than rewritten, so the two branches stay diffable. Not to be backported: `camel-4.22.x` already has all of this. _Claude Code on behalf of davsclaus_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
