Flow registration within the script using `flow.register()`: If I use

flow.register(project_name='my-project', indempotency_key=flow.serialized_hash())

on prefect server will the version number still get bumped each time?

@Adam Everington I think you need to differentiate here between versioning and storage. When you register your flow and you build your flow storage at the registration time (the default is build=True: 

flow.register(project_name="your_project", build=True)

), then all the changes you made to the flow will be reflected in the storage so that your flow will be run in the most up-to-date “version” of it. For instance, when you use Docker storage, the register command will by default also build the image and publish a new version of the image to the registry. However, when it comes to Prefect Versioning, it will be by default incremented only if there is any change in the Flow’s metadata and flow structure - i.e. new tasks, edges, or changes in storage, run configuration, schedule. So, for instance, if you change your code within a task, this will not cause bumping up the version, but if you add a new task, it will bump up the version, regardless whether you add a serialized hash as idempotency key or not.