You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/06/01 09:27:00 UTC

[jira] [Resolved] (CAMEL-23648) check-container-versions workflow should regenerate metadata.json after updating container.properties

     [ https://issues.apache.org/jira/browse/CAMEL-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-23648.
---------------------------------
    Resolution: Fixed

> check-container-versions workflow should regenerate metadata.json after updating container.properties
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23648
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23648
>             Project: Camel
>          Issue Type: Task
>          Components: build system, camel-test-infra
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.21.0
>
>
> The check-container-versions.yml GitHub Actions workflow automatically bumps container image versions in container.properties files and creates PRs (e.g. PR #23619).
> After CAMEL-23643 landed, the generated metadata.json now includes a serviceVersion field extracted from container image tags in container.properties. When the workflow updates a container.properties file but does not regenerate metadata.json, the serviceVersion in metadata.json becomes stale. CI will then detect uncommitted generated file changes and fail the PR.
> The workflow should be updated to:
> 1. Set up JDK 17 and Maven
> 2. Regenerate test-infra/camel-test-infra-all/src/generated/resources/META-INF/metadata.json
> 3. Regenerate catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/test-infra/metadata.json
> 4. Include the regenerated files in the commit



--
This message was sent by Atlassian Jira
(v8.20.10#820010)