# Temporal Worker Versioning Strategey **URL:** \ **Category:** Community Support\ **Tags:** java-sdk, general-impl\ **Created:** [September 14, 2023, 10:34am UTC](https://community.temporal.io/t/temporal-worker-versioning-strategey/9476 "2023-09-14T10:34:15Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jxwang](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jxwang/32/4270_2.png) [@jxwang](https://community.temporal.io/u/jxwang)\ **Post date:** [September 14, 2023, 10:34am UTC](https://community.temporal.io/t/temporal-worker-versioning-strategey/9476/1 "2023-09-14T10:34:15Z")
Hi Temporal, I am referring this page for temporal worker versioning using build id. [Java SDK developer’s guide - Versioning | Temporal Documentation](https://docs.temporal.io/dev-guide/java/versioning#java-versioning-api) Should I keep the existing worker running and every time create a new worker with a new build id? And how should integrate with temporal sdk autoconfigure? Configurations such as: spring.temporal: workers: - task-queue: your-task-queue-name name: your-worker-name # unique name of the Worker. If not specified, Task Queue is used as the Worker name. workflow-classes: - your.package.YouWorkflowImpl activity-beans: - activity-bean-name1 Best regards, Jx ---
**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\ **Post date:** [September 19, 2023, 3:19am UTC](https://community.temporal.io/t/temporal-worker-versioning-strategey/9476/2 "2023-09-19T03:19:28Z")
Worker versioning is not yet supported via SpringBoot autoconfig module, see feature request [here](https://github.com/temporalio/sdk-java/issues/1856). > Should I keep the existing worker running and every time create a new worker with a new build id? > Yes you would need to start new worker(s) for a new build version