davsclaus opened a new pull request, #126:
URL: https://github.com/apache/camel-jbang-examples/pull/126
Moves the examples to Camel 4.23.0, the 4.23 items of #86.
- **CI tests with Camel 4.23.0.** `camel@apache/camel` defaults to the
latest LTS release (4.22.0), so the workflow pins `CAMEL_VERSION` with
`-Dcamel.jbang.version` for the CLI, and `CITRUS_CAMEL_JBANG_VERSION` /
`CITRUS_CAMEL_CLI_VERSION` for the integrations the Citrus tests start. The
same change is in #118; whichever merges second rebases cleanly.
- **ai/mcp-server** sets `mcp-server-title`, `mcp-server-description` and
`mcp-instructions`. The README explains them, says the server serves
`ai-resource` routes next to tools, and shows the 4.23.0 log lines ("serving
tools and resources", and the current line numbers).
- **contracts/openapi-server** keeps `/api`, but its README no longer says
the `servers` entry must have a path. On 4.23.0 an entry without one serves the
operations at the root, checked with a copy of the contract.
- **Catalog and CLI:** nothing in the repository uses `--camel-version`. The
4.23.0 CLI shows `teaches` in `camel run --example=<group>`, and `ciSkip` as
the 🤖 icon.
- **Catalog fix:** the catalog listed
`ai/ticket-classifier/tickets-out/*/T-*.json`. These are files the example
writes when it runs, not repository files, and fetching them from GitHub
returns 404. Regenerated.
The circuit-breaker (#81) and LangChain4j provider (#91) items are in their
own PRs, stacked on this one.
Tested locally with Camel 4.23.0: the mcp-server Citrus test passes when run
with the same command and environment as CI (the integration logs "Apache Camel
4.23.0"), and `initialize` returns the title, description and instructions.
_Claude Code on behalf of davsclaus_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
