ci: regenerate generated resources for 4.14.9-SNAPSHOT#24528
Merged
Conversation
The camel-4.14.x generated catalog and component metadata still embedded the previous 4.14.8-SNAPSHOT version after the branch was bumped to 4.14.9-SNAPSHOT, so every PR's full build regenerated these files and tripped the 'Fail if there are uncommitted changes' CI gate. Bump all version-stamped generated resources to 4.14.9-SNAPSHOT, and fix the single stale camel-test entry in camel-bom (4.14.8 -> 4.14.9-SNAPSHOT, aligning it with the other managed camel artifacts). Mechanical version bump only; no functional change. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
davsclaus
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regenerate stale generated resources on
camel-4.14.xCompanion to #24476 (which did the same for
camel-4.18.x). Thecamel-4.14.xbranch was bumped to4.14.9-SNAPSHOT, but the generated catalog and component metadata still embed the previous4.14.8-SNAPSHOTversion. Every PR that runs a full build therefore regenerates these files and trips the "Fail if there are uncommitted changes" CI gate (thebuild (17)/build (21)jobs go red on unrelated PRs).This bumps all version-stamped generated resources to
4.14.9-SNAPSHOTso the committed state matches a clean build.src/generated/…component descriptors,component.properties,camel-catalog/camel-catalog-consoleresources):4.14.8-SNAPSHOT→4.14.9-SNAPSHOT.bom/camel-bom/pom.xml: the single stalecamel-testentry (4.14.8→4.14.9-SNAPSHOT), aligning it with the other managed camel artifacts.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.xPRs.🤖 Generated with Claude Code on behalf of Andrea Cosentino