Repository navigation
Conversation
…mel 4.22.3-SNAPSHOT After the 4.22.2 release the generated BOMs still pinned every org.apache.camel artifact to the released 4.22.2, so the build mixed 4.22.2 and 4.22.3-SNAPSHOT Camel jars and CI did not test the maintenance branch against current Camel 4.22.x fixes.
davsclaus
approved these changes
Oct 26, 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
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.
Summary
This is the post-release regen of the generated BOMs on
camel-spring-boot-4.22.x, the same fix as the 4.18.x PR.After the 4.22.2 release,
camel-spring-boot-dependenciesandcamel-spring-boot-bomstill pinned all 536org.apache.camelartifacts to the released4.22.2, whilecamel-versionis4.22.3-SNAPSHOT. As a result, the Dailycamel-spring-boot-4.22.xjob tests against the 4.22.2 release instead of the current Camel 4.22.x branch. On 4.18.x this same state already breaks tests: once upstream upgraded Vert.x, the build mixed released and snapshot Camel jars and hit aNoSuchMethodError. 4.22.x is green today, but it is exposed to the same problem.The diff is the generators' output (
tooling/camel-spring-boot-dependencies-generatorandtooling/camel-spring-boot-bom-generator) and only changes versions,4.22.2→4.22.3-SNAPSHOT.Test plan
mvn install -pl tooling/camel-spring-boot-dependencies-generator,tooling/camel-spring-boot-bom-generator -amJsonPathPlatformHttpTest,VertxWebsocketSSLTestandVertxWebsocketSSLGlobalTestpass locally with the regenerated BOMClaude Code (Opus 5.5) on behalf of Federico Mariani