Hi all, I've got a question about the workflow for...
# ask-community
s
Hi all, I've got a question about the workflow for upgrading the version of Prefect you're working with. I'm doing an upgrade right now where my plan is to first upgrade the version that my prefect agents are running, and from there I'm going to update the version of prefect in the RunConfig images that my flows are running with; my main question is around what will happen if I update the RunConfig images to have a new version of prefect (in my case, 0.14.17) installed, but I don't yet re-register the actual flows themselves (so they'll still show as having been registered with the old version of prefect I've been using). Is there a huge cause for concern here? When you upgrade the version of prefect that you're "running", do you also need to make sure you re-register all of your flows?
I guess my question is more so, will this absolutely break my flows, or is this fine to do? I suspect that updating the prefect version in the execution environment but leaving the version of prefect registered with as-is isn't as much of a concern as updating the prefect version in the registration environment, while leaving the execution environment using the old version
d
Hi Sean! It wonโ€™t absolutely break your flows, but it may and it may in unexpected and weird ways. We recommend re-registering all of your Flows with the version of Prefect core that you intend to be available in the execution infrastructure. In general, my recommendation is to upgrade the version of core associated with a flow when you work on it
s
i just learned that the hard way but okay thank you for setting me straight ๐Ÿ˜Ž
๐Ÿ‘ 1
z
I would say there's not a huge cause for concern because we try not to break things but there are definitely some edge cases that could cause you some opaque troubles ๐Ÿ™‚