Croway opened a new issue, #1837: URL: https://github.com/apache/camel-website/issues/1837
## Problem The website publishes exact-version Camel CLI manifests (`static/camel-cli/releases/X.Y.Z.properties`) and `latest.properties`. There is no maintained alias for the latest LTS, or for the latest patch of a release line, although release pages already carry `kind: lts` in their front matter. Today `latest.properties` selects 4.23.0 while the current LTS is 4.22.2, and `lts.properties` returns 404. The Camel installers will gain `--version LTS` / `--version X.Y` selectors ([CAMEL-26345](https://issues.apache.org/jira/browse/CAMEL-26345)). They need these aliases. ## Proposal Extend `update-camel-cli-manifest.sh`, which already advances `latest.properties` forward-only, to also generate: | Manifest | Meaning | | --- | --- | | `latest.properties` | Newest published release (unchanged) | | `lts.properties` | Newest published release with `kind: lts` | | `X.Y.properties` (e.g. `4.22.properties`) | Newest published patch of that line | ## Acceptance criteria - Use numeric version ordering, never date or lexical order. Exclude draft and future releases, and only consider `category: camel` releases. - A patch on an older LTS line (e.g. 4.18.6 after 4.22.x) must not move `lts.properties` backwards. - Publish an alias only when its exact-version manifest exists. Fail visibly otherwise; don't silently pick another version. - Make generation repeatable, and check alias/version/checksum consistency in CI. - Update `content/download/camel-cli-launcher.md` and the download guidance with latest-release behaviour, LTS examples and exact pins. Add selector examples once the installer support from CAMEL-26345 is released. Relevant paths: `update-camel-cli-manifest.sh`, `content/releases/`, `static/camel-cli/releases/`, `content/download/`. Related: [CAMEL-26345](https://issues.apache.org/jira/browse/CAMEL-26345) (installer selectors), [CAMEL-26346](https://issues.apache.org/jira/browse/CAMEL-26346) (documentation). -- 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]
