luigidemasi opened a new issue, #76: URL: https://github.com/apache/camel-kit/issues/76
> Imported from [luigidemasi/camel-kit#145](https://github.com/luigidemasi/camel-kit/issues/145), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-07-12. > Closed by [luigidemasi/camel-kit#198](https://github.com/luigidemasi/camel-kit/pull/198), merged on 2026-09-01. --- ## Description The Maven release workflow updates project POM versions but does not update the default `camel.kit.version` in either JBang launcher: - `camel-kit-main/src/main/jbang/main/CamelKit.java` - `camel-kit-main/dist/CamelKit.java` The public JBang catalog executes the raw source file, so Maven resource filtering cannot provide the version at runtime. ## Steps to Reproduce 1. Run the Maven release workflow. 2. Compare the root POM version with the launcher's default `camel.kit.version`. 3. Observe that only the POM version was advanced. Historical examples include commits `572a6c24` and `cb716e28`. ## Expected Behavior The release process updates and verifies both launcher copies for the release version and subsequent development snapshot. ## Actual Behavior The Maven Release Plugin only updates POM files, allowing the launcher fallback to remain on an older version. ## Additional Context Follow-up from the review of PR luigidemasi/camel-kit#144. ### Acceptance Criteria - Automatically update the source and generated launchers during releases. - Verify their fallback matches the root Maven project version. - Preserve zero-configuration installation through the public JBang alias. - Cover both the release and next-development-version commits. Website impact: not required — this hardens release automation for existing behavior. -- 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]
