All Versions
59
Latest Version
Avg Release Cycle
7 days
Latest Release
-

Changelog History
Page 1

  • v2.3.2 Changes

    ✨ Enhancements

    🛠 Fixes

    Collections

    Contributors

  • v2.3.1 Changes

    ✨ Enhancements

    🛠 Fixes

    Collections

    Contributors

  • v2.3.0 Changes

    Exciting New Features 🎉

    • ➕ Add support for deploying flows stored in Docker images — #6574
    • ➕ Add support for deploying flows stored on GitHub — #6598
    • ➕ Add file system block for reading directories from GitHub — #6517
    • ➕ Add a context manager to disable the flow and task run loggers for testing — #6575
    • ➕ Add task run pages to the UI — #6570

    ✨ Enhancements

    • ➕ Add "cloud" to prefect version server type display — #6523
    • 👉 Use the parent flow run client for child flow runs if available — #6526
    • ➕ Add display of Prefect version when starting agent — #6545
    • ➕ Add type hints to state predicates, e.g. is_completed() — #6561
    • ➕ Add error when sync compatible methods are used incorrectly — #6565
    • 👌 Improve performance of task run submission — #6527
    • 👌 Improve performance of flow run serialization for /flow_runs/filter endpoint — #6553
    • ➕ Add field to states with untrackable dependencies due to result types — #6472
    • ⚡️ Update Task.map iterable detection to exclude strings and bytes — #6582
    • ➕ Add a version attribute to the block schema model — #6491
    • ➕ Add better error handling in the telemetry service — #6124
    • ⚡️ Update the Docker entrypoint display for the Prefect image — #655
    • ➕ Add a block creation link to prefect block type ls — #6493
    • 👍 Allow customization of notifications of queued flow runs — #6538
    • Avoid duplicate saves of storage blocks as anonymous blocks — #6550
    • ✂ Remove save of agent default infrastructure blocks — #6550
    • ➕ Add a --skip-upload flag to prefect deployment build — #6560
    • ➕ Add a --upload flag to prefect deployment apply — #6560
    • ➕ Add the ability to specify relative sub-paths when working with remote storage for deployments — #6518
    • Prevent non-UUID slugs from raising errors on /block_document endpoints — #6541

    • 👌 Improve Docker image tag parsing to support the full Moby specification — #6564

      🛠 Fixes

    • Set uvicorn --app-dir when starting Orion to avoid module collisions — #6547

    • 🚀 Resolve issue with Python-based deployments having incorrect entrypoint paths — #6554

    • 🛠 Fix Docker image tag parsing when ports are included — #6567

    • ⚡️ Update Kubernetes Job to use args instead of command to respect image entrypoints — #6581

      • Warning: If you are using a custom image with an entrypoint that does not allow passthrough of commands, flow runs will fail.

    • 🛠 Fix edge case in sync_compatible detection when using AnyIO task groups — #6602

    • ➕ Add check for infrastructure and storage block capabilities during deployment build — #6535

    • 🛠 Fix issue where deprecated work queue pages showed multiple deprecation notices — #6531

    • 🛠 Fix path issues with RemoteFileSystem and Windows — #6620

    • Fix a bug where RemoteFileSystem.put_directory did not respect local_path — #6620

    📚 Documentation

    • ➕ Add tutorials for creating and using storage and infrastructure blocks — #6608
    • ⚡️ Update tutorial for running flows in Docker — #6612
    • ➕ Add example of calling a task from a task — #6501
    • 📚 Update database documentation for Postgres to clarify required plugins — #6566
    • ➕ Add example of using Task.map in docstring — #6579
    • ➕ Add details about flow run retention policies — #6577
    • 🛠 Fix flow parameter name docstring in deployments — #6599

    Contributors

    Thanks to our external contributors!

    • @darrida
    • @jmg-duarte
    • @MSSandroid

  • v2.2.0 Changes

    Exciting New Features 🎉

    🛠 Fixes

  • v2.1.1 Changes

    🛠 Fixes

  • v2.1.0 Changes

    🚀 Build Deployments in Python

    📚 The new, YAML-based deployment definition provides a simple, extensible foundation for our new deployment creation experience. Now, by popular demand, we're extending that experience to enable you to define deployments and build them from within Python. You can do so by defining a Deployment Python object, specifying the deployment options as properties of the object, then building and applying the object using methods of Deployment. See the documentation to learn more.

    Simplified Agents & Work Queues

    📚 Agents and work queues give you control over where and how flow runs are executed. Now, creating an agent (and corresponding work queue) is even easier. Work queues now operate strictly by name, not by matching tags. Deployments, and the flow runs they generate, are explicitly linked to a single work queue, and the work queue is automatically created whenever a deployment references it. This means you no longer need to manually create a new work queue each time you want to want to route a deployment's flow runs separately. Agents can now pull from multiple work queues, and also automatically generate work queues that don't already exist. The result of these improvements is that most users will not have to interact directly with work queues at all, but advanced users can take advantage of them for increased control over how work is distributed to agents. These changes are fully backwards compatible. See the documentation to learn more.

    👌 Improvements and bug fixes

    🆕 New Collections

    Full Changelog: https://github.com/PrefectHQ/prefect/compare/2.0.4...2.1.0

  • v2.0.4 Changes

    🚀 Simplified deployments

    🚀 The deployment experience has been refined to remove extraneous artifacts and make configuration even easier. In particular:

    • 🚀 prefect deployment build no longer generates a  manifest.json file. Instead, all of the relevant information is written to the deployment.yaml file.
    • 🚀 Values in the deployment.yaml file are more atomic and explicit
    • Local file system blocks are no longer saved automatically
    • Infrastructure block values can now be overwritten with the new infra_overrides field

    💻 Start custom flow runs from the UI

    🚀 Now, from the deployment page, in addition to triggering an immediate flow run with default parameter arguments, you can also create a custom run. A custom run enables you to configure the run's parameter arguments, start time, name, and more, all while otherwise using the same deployment configuration. The deployment itself will be unchanged and continue to generate runs on its regular schedule.

    👌 Improvements and bug fixes

    • ⏱ Made timeout errors messages on state changes more intuitive
    • ➕ Added debug level logs for task run rehydration
    • ➕ Added basic CLI functionality to inspect Blocks; more to come
    • ➕ Added support for filtering on state name to prefect flow-run ls
    • Refined autogenerated database migration output

  • v2.0.3 Changes

    📚 This release contains a number of bug fixes and documentation improvements.

    Introducing prefect-dbt

    🚀 We've released prefect-dbt - a collection of Prefect integrations for working with dbt in your Prefect flows. This collection has been built as part of a partnership with dbt Labs to ensure that it follows best practices for working with dbt.

    👌 Improvements and bug fixes

    • Azure storage blocks can use .prefectignore
    • Resolved bugs and improved interface in the Orion client.
    • Resolved a bug in Azure storage blocks that would cause uploads to get stuck.
    • 👻 Resolved a bug where calling a flow in a separate thread would raise an exception.
    • 🚀 Resolved issues with loading flows from a deployment.
    • Corrected some erroneous type annotations.
    • 👍 Better handling of database errors during state transition validation.
    • 👍 Better sanitization of labels for Kubernetes Jobs.
    • 🛠 Fixes --manifest-only flag of prefect deployment build command to ensure that using this flag, the manifest gets generated, but the upload to a storage location is skipped.
    • ➕ Added support for multiple YAML deployment paths to the prefect deployment apply command.

  • v2.0.2 Changes

    🚀 This release implements a number of improvements and bug fixes in response to continued engagement by members of our community. Thanks, as always, to all who submitted ideas on how to make Prefect 2 even better.

    Introducing .prefectignore files

    .prefectignore files allow users to omit certain files or directories from their deployments. Similar to other .ignore files, the syntax supports pattern matching, so an entry of *.pyc will ensure all .pyc files are ignored by the deployment call when uploading to remote storage. Prefect provides a default .prefectignore file, but users can customize it to their needs.

    👌 Improvements and bug fixes

    • 👉 Users can now leverage Azure storage blocks.
    • 👉 Users can now submit bug reports and feature enhancements using our issue templates.
    • Block deletion is now more performant.
    • 🚚 Inconsistencies in UI button copy have been removed.
    • 🚀 Error messaging is clearer in the deployment build CLI command.
    • 🔀 Resolved timeout errors that occurred when using async task functions inside synchronous flows.

  • v2.0.1 Changes

    🚀 The response to Prefect 2 has been overwhelming in the best way possible. Thank you to the many community members who tried it out and gave us feedback! Thanks in particular to the students at this week's Prefect Associate Certification Course (PACC) in San Jose for their thoughtful recommendations. This release is a compilation of enhancements and fixes that make for a more resilient, performant, and refined Prefect experience.

    👌 Improvements and bug fixes

    • 🚀 Schedules set via the API or UI are now preserved when building deployments from the CLI
    • 👍 JSON types are now coerced to none, following Javascript convention and supporting standards compatibility
    • 🚀 The prefect deployment execute command has been removed to avoid confusion between running a flow locally from a Python script and running it by an agent using prefect deployment run
    • This repository now includes templates for pull requests and issues to make bug reports and community contributions easier
    • ⏱ The scheduler and flow-run-notifications LoopServices have been made more resilient
    • 🌲 Log inserts have been made more performant through smaller log batches
    • 💻 Local file system blocks created from the UI now point to the right base_path
    • 👌 Support for unmapped values to Task.map has been added as requested by Club42 members
    • 🚀 The deployment build command now supports an optional output flag to customize the name of the deployment.yaml file, to better support projects with multiple flows