Flyte creates a new workflow version when you register code changes using commands like

pyflyte register

or

pyflyte run --remote

. Any modification to the workflow's code, structure, or dependencies results in a new version being registered, ensuring reproducibility and traceability of changes. Each registration captures the current state of the workflow, and you can view all versions in the Flyte UI or via the CLI, allowing you to run or roll back to any previous version as needed. This versioning is automatic and tied to the registration process, not to every code change in your local files—only when you explicitly register the workflow does a new version get created, reflecting the latest code and configuration at that time. For more details on how registration and versioning work, see the Registering workflows guide and the . Would you like more detail on how Flyte determines what constitutes a new version or how to manage versions? Sources: - Registering workflows guide - Figure Image 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.