prefect

This release fixes a critical bug in the SQLite database migrations in 2.7.4 and 2.7.5. See https://github.com/PrefectHQ/prefect/issues/8058 for details.

Note this release does not include any other changes from the main branch since 2.7.5. It is a backport of the migration bug fix.

WARNING: This release includes a bug in SQLite data migrations which will result in loss of historical state data.
This release has been yanked from the Python package index. See https://github.com/PrefectHQ/prefect/issues/8058 for details.

This release adds two features to the CLI: retrieval of flow run logs and the ability to schedule a flow run for a execution in the future. This release also highlights some updates in our GCP, Airbyte, and DBT collections!

See the release notes for details.

WARNING: This release includes a bug in SQLite data migrations which will result in loss of historical state data.
This release has been yanked from the Python package index. See https://github.com/PrefectHQ/prefect/issues/8058 for details.

This release greatly expands control over retry delays, including exponential backoffs and jitter! We've also added support for experimental flags behind the scenes, so expect to see some experimental features soon 👩‍🔬

See the release notes for details.

This release includes some bug fixes 🐞

See the release notes for details.

This release adds rescheduling of paused flow runs, pausing flow runs from the UI, a new page for viewing individual task run concurrency limit details, and many other enhancements and fixes :)

We've also added new collections for Bitbucket and Kubernetes!

See the release notes for more details.

This release adds a new setting for using custom blocks, improves cancellation edge-cases, a new task concurrency page, and adds bulk deletion to more objects in the UI!

See the release notes for details and bug fixes!

It's only been a little over a week since the last release, but there are a lot of new features we're excited to announce!

This release includes:

• Cancellation of flow runs
• Pause and resume of flow runs
• Logging of print statements
• Agent-level flow run concurrency limits
• Notification blocks for PagerDuty and Twilio
• Improved reporting of crashed infrastructure
• Improved handling of failures during HTTP requests
• ... and dozens more fixes and enhancements!

Thanks a bunch to our five external contributors ❤️

See the release notes for examples and more details.

This release includes big updates to the Prefect Cloud login experience as well as improvements to logging (e.g. task run logs on remote workers are sent to the API now).

See the release notes for details!

This release includes new agent options, many bug fixes, and the announcement of a newprefect-vault collection.

See the release notes for details.

This release adds timeouts for task runs, colored logging, obfuscation of secret settings, dark mode for documentation, and more! It also includes usability updates in the UI, performance improvements for the scheduler, and lots of bug fixes.

See the release notes for more details 🎉

This release adds status displays for work queue health to the UI and support for waiting for upstream tasks before starting a subflow!

It also includes:

• Scheduler performance improvements
• Documentation for our versioning scheme
• Three new collections: GitLab, Alerts, and Fivetran!

See the full release notes for more details.

This release includes bug fixes and enhancements to the core library. The highlights are:

• Support for manual flow run retries
• Improved server performance when retrying flow runs with many tasks
• Status checks in work queues
• Support for Python 3.11

See the release notes for details.

This release includes bug fixes and enhancements to the core library, but the highlights are in our collections. There's a new infrastructure block for running flows in containers on Azure, a new key-value store collection, and the ECS infrastructure block has been designated as ready for production.

See the release notes for details.

By the way, if you haven't checked out 2.6 yet, you should now! We launched first-class configuration of results in 2.6.0 and every release since includes additional improvements to result handling.

This release fixes a bug in 2.6.2 where Task.with_options could fail due to a null value for the new cache_result_in_memory setting.

This release includes some major enhancements, including support for compound recurrence rule schedules and private GitHub repositories. There are also fixes and enhancements for the new results feature; notably, we now support reducing memory consumption by optionally always retrieving results from storage.

As always, the highlights above are a small subset of the changes. See the release notes for everything else!

This release patches a bug where flow and task return values of {} or [] could be incorrectly coerced to None.

👋 This release includes some big features like first-class configuration of results, waiting for failed tasks, specifying an agent's work queues with a prefix string, and setting parameters when running deployments from the CLI. There are also a bunch of fixes and performance improvements.

Check out the release notes for examples and more details.

This release includes the ability to easily orchestrate flow runs for deployments from other flow runs! If you're currently using OrionClient.create_flow_run_from_deployment, or if that's been too complicated, you'll be excited to see our sync-compatible run_deployment function that links created runs as subflows. There are a bunch of other enhancements and fixes too! Check out the release notes for details.

This release disables block protection. With block protection enabled, as in 2.4.3 and 2.4.4, client and server versions cannot be mismatched unless you are on a version before 2.4.0. Disabling block protection restores the ability for a client and server to have different version.

Block protection was added in 2.4.1 to prevent users from deleting block types that are necessary for the system to function. With this change, you are able to delete block types that will cause your flow runs to fail. New safeguards that do not affect client/server compatibility will be added in the future.

Note this release also restores block memoization by default, reverting the change in 2.4.4 as it did not patch the issue as intended.