Prefect 1.0 - Why Prefect don’t recommend forcing version update when the flow metadata didn’t change? Having an updated timestamp on the flow helps user understand when the flow was updated without going back to git repos or CI/CD pipelines logs.

by default when your metadata doesn't change, your version doesn't get incremented

yes, I understand the default behavior and we can force version bump, but just curious on why it’s the default behavior

it's explained on Discourse

If I understand correctly, if we moved to pickled storage, the version number and the timestamp will change every time we modify and register the flow source code. The pros with pickled storage is it “froze your flow at registration time”. The cons are it’s easier to break between Prefect version upgrades. So forcing the flow registration with script based storage fits our use case. Will there be performance limitations with forcing registrations since that’ll generate a ton of versions?

no, it won't

sounds great! Thank you!