claudio4j opened a new pull request, #4731: URL: https://github.com/apache/camel-k/pull/4731
Fix https://github.com/apache/camel-k/issues/4715 <!-- Description --> * Upgrade semver api to v3 * `kamel version -a` relies on loading the catalog using the runtime provider, which is not set in the IntegrationPlatform object, so rendering null and not loading the CamelCatalog object. * It may occur the CamelCatalog object is not in the same namespace of the camel-k-operator pod, so we should not print an error message in case the CamelCatalog is not found. * In the catalog initialization, print any error related to building the container image in the camel-k-operator log as the error was set only in the CamelCatalog status object. * Change the `RuntimeVersion` type of CamelCatalog object to string, as there may be cases of the runtime version not following the semantic version. * The `findBestMatch` was renamed to `findCatalog`, since it was not actually trying to match a version rule, but plainly using a full version to check it. <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure the text is added to the right section of the release notes. --> **Release Note** ```release-note Update semver golang api to v3 ``` -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
