[
https://issues.apache.org/jira/browse/CAMEL-23376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Cunningham updated CAMEL-23376:
--------------------------------------
Description:
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.
was:
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 commit afterwards so that all the json and properties files
get regenerated with the new -SNAPSHOT version.
> 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
> Priority: Major
>
> 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)
