oscerd opened a new pull request, #24528: URL: https://github.com/apache/camel/pull/24528
## Regenerate stale generated resources on `camel-4.14.x` Companion to #24476 (which did the same for `camel-4.18.x`). The `camel-4.14.x` branch was bumped to `4.14.9-SNAPSHOT`, but the generated catalog and component metadata still embed the previous `4.14.8-SNAPSHOT` version. Every PR that runs a full build therefore regenerates these files and trips the **"Fail if there are uncommitted changes"** CI gate (the `build (17)` / `build (21)` jobs go red on unrelated PRs). This bumps all version-stamped generated resources to `4.14.9-SNAPSHOT` so the committed state matches a clean build. - **1886** generated files (`src/generated/…` component descriptors, `component.properties`, `camel-catalog` / `camel-catalog-console` resources): `4.14.8-SNAPSHOT` → `4.14.9-SNAPSHOT`. - **`bom/camel-bom/pom.xml`**: the single stale `camel-test` entry (`4.14.8` → `4.14.9-SNAPSHOT`), aligning it with the other managed camel artifacts. - Verified every changed line is the version bump and nothing else; the `salesforce-component.adoc` "Starting with Camel 4.14.8" prose reference is deliberately left untouched. Mechanical version bump only; no functional change. CI's own full build + uncommitted-changes gate validates completeness — a green run confirms the committed state matches a fresh build. After this merges, the uncommitted-changes gate should be green again for `camel-4.14.x` PRs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) on behalf of Andrea Cosentino -- 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]
