Croway opened a new pull request, #1838:
URL: https://github.com/apache/camel-website/pull/1838

   Refs #1837
   
   Publishes `lts.properties` (newest LTS release) and `X.Y.properties` (newest 
patch per line) next to the existing `X.Y.Z.properties` / `latest.properties`. 
The Camel CLI installers' `--version LTS` / `--version X.Y` selectors need them 
(apache/camel#28582, CAMEL-26345).
   
   - `update-camel-cli-manifest.sh`:
     - reads `kind:` / `draft:` / `category:` from 
`content/releases/release-<version>.md` and passes `--lts true` for LTS releases
     - fails if the page is missing, is a draft, or isn't `category: camel`
     - runs the alias check at the end
     - new `CAMEL_GENERATOR_SRC` / `CAMEL_INSTALL_SRC_DIR` env vars use a local 
generator and installers instead of fetching them from apache/camel main
   - `scripts/camel-cli-aliases.sh check|rebuild|kind` derives the LTS list 
from the release pages and calls the generator's rebuild mode.
   - `scripts/WebsiteManifestGenerator.java` re-vendored from the apache/camel 
PR (banner + byte-identical body).
   - Backfill: `lts.properties` -> 4.22.2, and `4.13` ... `4.23` -> the newest 
patch of each line. `latest.properties` is unchanged (4.23.0).
   - CI: a `camel-cli-manifests` job in `pr.yaml` runs the drift check.
   - `content/download/camel-cli-launcher.md`: describes the manifests and that 
the default is the latest release, not the LTS. Selector instructions will come 
once a Camel release ships them.
   
   `static/install.sh` / `install.ps1` are unchanged here. They get re-vendored 
by the usual script after the apache/camel change is released.
   
   Merge after the apache/camel PR, so the vendored generator matches main.
   
   Testing: the alias check passes on this content, and it detects an altered 
`lts.properties`. The generator was also exercised end to end (publish 
sequence, older-LTS patch, conflicts) together with the installer selectors in 
a sandbox.
   


-- 
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]

Reply via email to