Croway opened a new pull request, #28582: URL: https://github.com/apache/camel/pull/28582
https://issues.apache.org/jira/browse/CAMEL-26345 https://issues.apache.org/jira/browse/CAMEL-26346 The web installers accepted only exact `X.Y.Z`. Users could not ask for "the latest LTS" or "the latest 4.22 patch", and `camel self-update` refused to move any pinned install. Today `latest.properties` is 4.23.0 while the LTS is 4.22.2. **Manifest aliases** (`WebsiteManifestGenerator.java`, which the website vendors): - `X.Y.properties` always advances forward-only. `lts.properties` advances with `--lts true`. Same conflict rules as `latest.properties`, and a patch on an older LTS line never moves `lts` back. - `--rebuild-aliases --output <dir> --lts-versions ... [--check]` regenerates every alias from the immutable `X.Y.Z.properties`. With `--check` it is a dry-run drift check for website CI. **Installers and self-update:** - `install.sh --version LTS | X.Y | X.Y.Z`, and the same for `install.ps1 -Version`. The resolved manifest is validated (`X.Y.*` for a line) before the existing checksum and staged activation run. - The pin file stores the selector. `camel self-update`: - exact pin: refuses, as today - `X.Y` pin: moves to the newest patch of that line - `LTS` pin: moves to the newest LTS - `--version` on a selector-pinned install: refused - The update notice checks the matching alias for selector pins. - No-argument installs and existing `X.Y.Z` pins are unchanged. An older CLI that finds a selector pin refuses `self-update`, so it fails safe. **Docs:** install, pinning, self-update and selector pages: the default is the latest release, not the LTS. The CLI version is kept distinct from `--camel-version`. Testing: - Unit: `camel-launcher` 285 tests, 0 failures. The 36 skipped are the Windows-only PowerShell and `camel.bat` tests, which need a Windows run. - End-to-end in a container against a local fake camel.apache.org + Maven layout, published step by step with this generator: bare / exact / line / LTS installs; `self-update` within a line and to a newer LTS; an older-line LTS patch not moving `lts`; invalid selectors; missing alias; tampered line alias and checksum (existing install untouched each time); update notice for a line pin; released 4.22.2 with an `LTS` pin refusing. - `install.ps1` under Linux pwsh up to the Windows-only activation step: selector validation, missing alias, line mismatch and LTS resolution with checksum. Website side (publishing the aliases): apache/camel-website#1837, PR to follow. -- 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]
