Add test to verify camel-latest-version property in pom.xml is aligned to recipes#103
Merged
JiriOndrusek merged 1 commit intoMay 13, 2026
Conversation
Croway
approved these changes
May 12, 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.
fixes #97
Add automated test to verify camel-latest-version property
Adds LatestCamelVersionTest to automatically verify that the camel-latest-version property in pom.xml
matches the highest version recipe file (e.g., 4.20.0 ↔ 4.20.yaml).
The test fails during CI if a new version recipe is added without updating the property, preventing the
issue where users migrating to "latest" would get an outdated version.
Because of the similarity with the
LatestRecipeTestfrom the b36b25e. The commoncode was moved intoRecipeVersionhelper class.