[ 
https://issues.apache.org/jira/browse/CAMEL-27352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-27352:
--------------------------------
    Fix Version/s: 4.25.0
                       (was: 4.24.0)

> camel-jbang - upgrade view and command showing the state of upgrading an 
> integration to a newer Camel release
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-27352
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27352
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 4.25.0
>
>
> A new view in camel-jbang (and a CLI command) that shows the state of 
> upgrading an integration to a newer Camel release. It is read-only: it 
> gathers the facts an upgrade needs, and the actual migration stays with camel 
> update run (OpenRewrite recipes) and later Camel Kit.
> *Where you are*
> * Camel version in use, LTS or not, EOL date, days since release, the latest 
> patch of the same line, the latest LTS, the latest release, and the JDK each 
> needs (camel-releases.json of the catalog). The target defaults to the latest 
> patch of the line, and can be changed to any newer release.
> *Why move*
> * The Apache Camel security advisories that affect the version in use, and 
> the release that fixes each (SecurityAdvisoryHelper, as in the CVE audit).
> * CVEs of Camel-managed third-party libraries that the target release fixes.
> *What breaks*
> * The upgrade guide entries between the version in use and the target, 
> filtered to the components the routes use (the guides have a section per 
> component).
> * Components the integration uses that are deprecated or removed in the 
> target (for example pipes, removed in 4.24).
> * A changed JDK minimum (4.24 needs Java 21).
> * Third-party libraries the integration relies on whose version takes a major 
> step between the two camel-parent POMs (for example kafka-clients 3.x to 4.x).
> *What camel update would change*
> * The recipes that apply between the two versions (camel update list), as a 
> preview.
> *Try it*
> * Run the integration on the target version (camel run --camel-version=X) 
> next to the one in use, and compare startup, errors and routes.
> *AI*
> * Shift+F8: plan this upgrade, with the facts above in the prompt. No change 
> to the files unless the user agrees.
> *CLI*
> * The same report as a command, for example camel upgrade check 
> [--to=<version>] [--json], with the CLI exit codes, sharing the code with the 
> view.
> Related: CAMEL-27351, CAMEL-27328, CAMEL-27340.
> _Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to