You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2026/09/11 07:43:00 UTC

[jira] [Updated] (CAMEL-23376) Add a refresh commit to the release process

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

Guillaume Nodet updated CAMEL-23376:
------------------------------------
    Fix Version/s: 4.23.0

> Add a refresh commit to the release process
> -------------------------------------------
>
>                 Key: CAMEL-23376
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23376
>             Project: Camel
>          Issue Type: Task
>          Components: build system
>            Reporter: Thomas Cunningham
>            Assignee: Guillaume Nodet
>            Priority: Minor
>             Fix For: 4.23.0
>
>
> Would it be possible to add a refresh commit as part of the release process after the new SNAPSHOT version is set?      
> I've noticed on camel and camel-spring-boot that the release process does a versions:set that bumps the versions to the next SNAPSHOT but we always need to submit a refresh PR afterwards so that all the json and properties files get regenerated with the new -SNAPSHOT version.



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