Bump prefect from 2.11.0 to 2.14.3 in /examples/simple

[dependabot]

Bumps prefect from 2.11.0 to 2.14.3.

Release notes

Sourced from prefect's releases.

Release 2.14.3

Deployment Status Monitoring 🚦

• Track deployment status in the Prefect UI
• Emit Prefect Cloud events for deployment status changes, with automation triggers available

Expanded Storage for flow.from_source 🗂

• Load flows from remote storage locations like S3 and Azure Blob Storage using fsspec protocols

Enhancements and Fixes 🔧

• Skip Docker builds with flow.deploy
• Fixes for cancellation cleanup, Pydantic V2 models in flow signatures

Documentation and Guides 📘

• Adds documentation for Systemd daemonization, global concurrency clarification, and Prefect Cloud teams

See the release notes for details!

Release 2.14.2

This release includes the ability to pass **kwargs to state change hooks 🪝, allowing you to further customize the actions you to take upon completion or cancellation. Additionally, we've improved the management of on_cancellation and on_crashed flow run state change hooks.

See the release notes for details!

Release 2.14.1

This release includes:

🪲 Fixes

• Refined flow parameter validation to use the correct validation depending on if the parameter is a pydantic v1 or v2 model.

📚 Documentation Improvements

• Added Python serve and deploy options to the schedules concepts documentation

See the release notes for details!

Release 2.14.0

This release includes:

🌐 prefect-client

This slimmed down version of prefect has a small surface area of functionality and is intended for interacting with the Prefect server or Prefect Cloud only. It is ideal for use in lightweight, ephemeral execution environments when the goal is to interact with Prefect API resources. It is now installable via pip:

pip install prefect-client

🏷 Flow Labels for Subflow Runs We've improved the Prefect UI by adding flow names to subflow runs.

🪲 Windows Environment Compatibility We've fixed issues related to pulling flows and building deployments in Windows environments.

... (truncated)

Changelog

Sourced from prefect's changelog.

Release 2.14.3

Observability with deployment status

You can now track the status of your deployments in the Prefect UI, which is especially useful when serving flows as they have no associated work pool or worker. If you see a flow run enter a LATE state (it isn’t running), you can click into the deployment for that flow run and see a red indicator next to your deployment. The worker, runner, or agent polling that deployment or its associated work queue is offline.

• Deployments created from served flows will have a READY status if its associated process is running.
• Deployments created in a work pool will have a READY status when a worker is ONLINE and polling the associated work queue.
• Deployments created in a push work pool (Prefect Cloud) will always have a READY status.

In Prefect Cloud, an event is emitted each time a deployment changes status. These events are viewable in the Event Feed.

You can also create an automation triggered by deployment status changes on the Automations page!

See the following pull requests for implementation details:

• PrefectHQ/prefect-ui-library#1801
• PrefectHQ/prefect#10969
• PrefectHQ/prefect#10951
• PrefectHQ/prefect#10949

Additional storage options for flow.from_source

You can now load flows from a variety of storage options with flow.from_source! In addition to loading flows from a git repository, you can load flows from any supported fsspec protocol.

Here's an example of loading and serving a flow from an S3 bucket:

from prefect import flow
if name == "main":
flow.from_source(
source="s3://my-bucket/my-folder",
entrypoint="flows.py:my_flow",
).serve(name="deployment-from-remote-flow")

You can use the RemoteStorage class to provide additional configuration options.

Here's an example of loading and serving a flow from Azure Blob Storage with a custom account name:

... (truncated)

Commits

• f1ff925 prep release notes v2.14.3 (#11084)
• 816aafc Update global concurrency docs to be more global (#11074)
• d903ef3 Updates UI packages (#11086)
• 9371d10 Add generic remote storage for flow.from_source using fsspec (#11072)
• 418b63b docs: add clarifying comment on use of task (#11085)
• a093cf9 Add option to skip building a Docker image with flow.deploy (#11082)
• cf3f328 Fix bug where runner can't load remotely stored flow when running hooks (#11077)
• 5516542 Update cloudpickle requirement from <3.0,>=2.0 to >=2.0,<4.0 (#11023)
• 9eef11a Use expected_start_time in Graph v2 for unstarted runs (#11070)
• a468ce8 Warn if task parameter introspection takes a long time (#11075)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.