luigidemasi opened a new issue, #88:
URL: https://github.com/apache/camel-kit/issues/88

   > Imported from 
[luigidemasi/camel-kit#209](https://github.com/luigidemasi/camel-kit/issues/209),
 opened by [luigidemasi](https://github.com/luigidemasi) on 2026-09-04.
   > Closed on 2026-09-04 without a linked pull request.
   
   ---
   
   ## Description
   
   Camel-Kit still defaults Camel Main, Spring Boot, and Camel MCP to `4.21.0`, 
which is no longer a supported upstream line. Move the default to the current 
`4.22.0` LTS and refresh the supported Main/Spring Boot matrix to the two 
active LTS lines.
   
   This release update also removes the repeated version literals that made 
every release unnecessarily broad. `distribution.properties` remains the 
reviewed source of truth; generated configuration, shipped guidance, and 
policy-dependent tests must derive their values from it.
   
   The Camel Quarkus matrix is independent and is intentionally unchanged by 
this issue.
   
   ## Resolved compatibility matrix
   
   | Runtime / integration | Camel | Paired version |
   |---|---:|---:|
   | Main default | `4.22.0` | Forage `1.6.0` |
   | Main supported LTS | `4.18.4` | Forage `1.4.1` |
   | Spring Boot default | `4.22.0` | Spring Boot `4.1.0`, Forage `1.6.0` |
   | Spring Boot supported LTS | `4.18.4` | Spring Boot `3.5.16`, Forage 
`1.4.1` |
   | Camel MCP | `4.22.0` | — |
   
   The `4.14.x` Main/Spring Boot entries are dropped because that line is no 
longer supported upstream. Existing Quarkus entries, including the Quarkus-only 
Forage mapping, remain unchanged.
   
   ## Implementation
   
   ### Centralized version ownership
   
   - Keep every distribution pin and compatibility row in 
`distribution.properties`.
   - Remove embedded production fallback version literals from 
`DistributionConfig`; the bundled properties resource is mandatory and fails 
fast if incomplete.
   - Generate MCP coordinates, supported-version guidance, Forage tables, and 
other shipped template content from the same loaded distribution data.
   - Derive policy-dependent test fixtures and the packaged Ship certification 
matrix from the distribution data. Keep explicit compatibility rows and content 
hashes as reviewed evidence rather than discovering them dynamically.
   - Retain only the `camel.main.version` POM mirror that Maven needs before 
lifecycle plugins can load `distribution.properties`. Maintain it with a small 
idempotent sync/check helper and a drift test.
   
   ### Release matrix and Ship evidence
   
   - Update Main, Spring Boot, Spring Boot BOM, and Camel MCP defaults to 
`4.22.0`.
   - Set Main/Spring Boot supported versions to `4.22.0,4.18.4`.
   - Record the verified Spring Boot, Forage, JSON-schema-validator, Citrus, 
and catalog inventory rows for both supported Camel versions.
   - Preserve Ship v1's Simple-only expression contract. Camel 4.22 adds Jactl 
to the catalog, so the catalog classifier must recognize `jactl` and reject it 
explicitly instead of allowing it to evade the non-Simple check. Supporting 
Jactl would require a separate policy, validation, and threat-model change.
   
   ### Documentation and knowledge
   
   - Update core documentation/examples and the companion website pages to 
4.22.0 and the refreshed compatibility matrix.
   - Complete 
[camel-kit-knowledge#13](https://github.com/luigidemasi/camel-kit-knowledge/issues/13)
 and build/publish a 4.22 documentation index. The existing policy retains the 
latest non-LTS corpus alongside active LTS lines, so 4.21 remains historical 
search coverage there.
   - The core and website changes may merge independently, but this issue and 
the 4.22 release remain open until the knowledge index is available.
   
   ## Implementation pull requests
   
   - Core: [camel-kit#210](https://github.com/luigidemasi/camel-kit/pull/210)
   - Knowledge: 
[camel-kit-knowledge#14](https://github.com/luigidemasi/camel-kit-knowledge/pull/14)
   - Website: 
[camel-kit-web#36](https://github.com/luigidemasi/camel-kit-web/pull/36)
   - Knowledge tracker: 
[camel-kit-knowledge#13](https://github.com/luigidemasi/camel-kit-knowledge/issues/13)
   
   ## Acceptance criteria
   
   - [x] `distribution.properties` is the source of truth for all distribution 
versions and contains the exact matrix above; Quarkus rows are unchanged.
   - [x] Production Java and shipped templates contain no duplicated 
release-specific Main/Spring Boot/MCP values; the necessary Maven mirror is 
generated and checked for drift.
   - [x] The narrowed current-release surface contains no stale `4.21.0` or 
`4.18.3` values outside changelog history or deliberately historical 
documentation.
   - [x] Generated outputs prove the MCP coordinate, supported-version 
guidance, security guidance, and Forage table reflect the distribution data.
   - [x] Ship's committed catalog inventory has exact `4.22.0` and `4.18.4` 
rows; deterministic packaged-row certification passes for both.
   - [x] Jactl is recognized as a Camel 4.22 language selector and rejected 
with Ship's Simple-only policy message.
   - [x] Main and Spring Boot smoke projects persist the expected 4.22.0 
configuration and resolve their corresponding runtime dependencies; the Camel 
MCP 4.22 runner answers a catalog probe with `camelVersion=4.22.0`.
   - [x] `./mvnw -B clean install` and the source checks pass.
   - [x] The companion website build passes and the public version 
examples/tables match the matrix.
   - [x] A companion knowledge issue and implementation PR are linked; the 
rebuilt manifest contains 30,520 documents across Camel 4.18 through 4.22.
   - [x] The 4.22 index is published before this issue is closed or the release 
is cut.
   
   ## Website impact — Required
   
   Update `content/architecture/camel-mcp.md`, 
`content/architecture/forage.md`, `content/architecture/graph.md`, 
`content/reference/commands.md`, and the Knowledge MCP index statistics in 
`camel-kit-website`.
   


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