zbendhiba opened a new pull request, #28850: URL: https://github.com/apache/camel/pull/28850
## Upgrade-guide notes for the Swift header rename on the 4.18 and 4.22 lines Follow-up to #28231 (CAMEL-25895), which renamed the four remaining `SwiftConstants` Exchange header constants on `main`. That change is backported to `camel-4.18.x` and `camel-4.22.x`, so it ships in **4.18.6** and **4.22.3** as well as 4.24.0. The upgrade guides for every version live on `main` and act as the canonical history across releases, so the per-line notes belong here rather than on the maintenance branches. - **Jira:** [CAMEL-25895](https://issues.apache.org/jira/browse/CAMEL-25895), fixVersions 4.18.6, 4.22.3, 4.24.0 - **Backport PRs:** #28280 (`camel-4.22.x`) and #28281 (`camel-4.18.x`), both merged ### Changes | File | Change | |---|---| | `camel-4x-upgrade-guide-4_18.adoc` | new `=== camel-openstack` note at the end of `== Upgrading from 4.18.5 to 4.18.6`, naming 4.18.3 as the release that kept the openstack4j values on that line | | `camel-4x-upgrade-guide-4_22.adoc` | the same note at the end of `== Upgrading from 4.22.2 to 4.22.3`, naming 4.21 | | `camel-4x-upgrade-guide-4_18.adoc`, `camel-4x-upgrade-guide-4_21.adoc` | the `NOTE` added by #28231 pointed at the Jira issue for the releases carrying the rename; it now names 4.18.6, 4.22.3 and 4.24.0 directly | Each note carries the constant table, the reason the previous values were kept and why that reason does not hold (openstack4j builds the `X-Container-*` wire names itself, so the request Camel sends to Swift is unchanged by the rename), the migration for routes that set the header by its literal string value, and the renamed Endpoint DSL accessors. Docs only, under `docs/user-manual`. No component `src/main/docs` page is touched, so there is no catalog copy to regenerate. No new `xref:` links and no explicit `[[anchor]]` blocks are added. -- 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]
