Prefect 2.0 and Prefect Cloud 2.0 have exited their public beta and launched in general availability! πŸš€

We’re thrilled to announce that Prefect 2.0 and Prefect Cloud 2.0 have exited their public beta and launched in general availability! :tada:

(Re)Introducing Prefect

Hopefully, this release comes as no surprise. It is the culmination of nearly a year of building in public and incorporating your feedback. Even still, the Prefect 2.0 release is just the latest step in a journey that goes much further.

Prefect 2.0 is the most Pythonic, dynamic orchestrator ever - but orchestration alone is just one of many needs that the modern data stack demands. With recent enhancements that enable you to leverage the simplicity of Prefect 2.0’s observability without handing over control of your dataflows to the orchestration engine, Prefect 2.0 is the first coordination plane - a single layer that enables you to observe, alert, orchestrate, and respond to dataflows between and across applications. Learn more in our GA announcement post:

Immediate changes

With this release, the following changes have taken effect:

All of the URLs for Prefect Cloud 1.0, Prefect Cloud 2.0, and our documentation will be unchanged or will redirect:

We will continue to support both Prefect 1.0 and Cloud 1.0.

Upgrading from Prefect 1.0 to Prefect 2.0

Flows written with Prefect 1.0 will require modifications to run with Prefect 2.0. If you’re using Prefect 1.0, you can make the transition to Prefect 2.0 when the time is right for you.

Please see the following topic for explicitly pinning your Prefect version in your package manager and Docker:

https://discourse.prefect.io/t/the-general-availability-release-of-prefect-2-0-going-live-on-wednesday-27th-of-july-may-break-your-flows-unless-you-take-action-as-soon-as-possible/1227

To learn more about upgrading, see our migration guide:

13 Likes