# New Temporal worker versioning

**URL:** <https://community.temporal.io/t/new-temporal-worker-versioning/13032>\
**Category:** Community Support\
**Tags:** java-sdk, general-impl\
**Created:** [August 1, 2024, 10:10am UTC](https://community.temporal.io/t/new-temporal-worker-versioning/13032 "2024-08-01T10:10:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [August 6, 2024, 3:02pm UTC](https://community.temporal.io/t/new-temporal-worker-versioning/13032/4 "2024-08-06T15:02:06Z")

</div>

Hi @jxwang

yes, you are right part of the workflows will go to A1, as defined in the rule

Have you considered using one of the other versioning strategies for this case? Either [Workflow name based Versioning](https://community.temporal.io/t/workflow-versioning-strategies/6911#workflow-name-based-versioning-3) or [Task Queue based Versioning](https://community.temporal.io/t/workflow-versioning-strategies/6911#task-queue-based-versioning-replaced-by-worker-versioning-4)?

Antonio

---

_[View the full topic](https://community.temporal.io/t/new-temporal-worker-versioning/13032)._