Croway commented on PR #132: URL: https://github.com/apache/camel-upgrade-recipes/pull/132#issuecomment-6290271330
CI on 4116d25 was red for two reasons: - `CamelSpringBoot423Test.migrateLangchain4jToolsStarterDependency`: Maven Central answered HTTP 502 while the parser resolved `io.prometheus:simpleclient_bom:0.16.0`, a transient network error. - `CamelSpringBootBomVersionTest` (2/3): its expectation encoded the Maven-parser warning marker of the unresolvable `4.23.0-SNAPSHOT` BOM, and the version chain now running after the bumps adds two more markers (every recipe that touches the POM afterwards warns again, and the markers differ by stack trace). The same test fails locally whenever the SNAPSHOT BOM is cached in `~/.m2`, and the hard-coded `4.23.0-SNAPSHOT` would have failed `release:prepare`. b369ae7 makes the test run `CamelSpringBoot418LTSMigrationRecipe` instead, whose target is a released version, as `CamelSpringBootParentVersionTest` already does, and adds a yaml-level check that every aggregate (`latest.yaml`, `*LTS.yaml`) sets the `camel-spring-boot-version` / `camel.springboot.version` / `camel-spring-boot.version` properties to the BOM version it upgrades to. `4.18LTS.yaml` gains those `ChangePropertyValue` entries, which `latest.yaml` already had. _Claude Code on behalf of croway_ -- 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]
