Hey @ancient-wolf-19325 Can I register a flyte workflow package without specifying the version all the time? I want to create a ci/cd flow for packaging and registering the workflow package, where always setting and distributing the version (like a unique hash) tedious. What do you recommend ?

No, Flyte requires a version to be specified when registering workflows, tasks, or launch plans. If you do not provide a version, registration will fail with an error indicating a missing version. This is by design to ensure reproducibility and traceability of all entities in Flyte. Automating version generation (e.g., using a git commit hash) in your CI/CD pipeline is the recommended approach, as shown in the official documentation and community discussions. There is no built-in mechanism to auto-generate or default the version if omitted during registration—manual or scripted assignment is necessary for each registration step. According to the documentation, the typical pattern is to use a unique string (often the git SHA) as the version in CI/CD, for example: --version "$(git rev-parse HEAD)" when running flytectl register files. This ensures each registration is uniquely identifiable and supports rollback and reproducibility. Omitting the version is not supported and will result in errors during registration (docs/user_guide/flyte_fundamentals/registering_workflows.md, github issue #1968). Would you like more detail on how to automate versioning in your CI/CD pipeline? Sources: - docs/user_guide/flyte_fundamentals/registering_workflows.md - github issue #1968 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.