Bump prefect from 2.13.5 to 2.13.7

[dependabot]

Bumps prefect from 2.13.5 to 2.13.7.

Release notes

Sourced from prefect's releases.

Release 2.13.7

This release includes:

⚙️ 🥳 Pydantic V2 Support

In #10946 we add support for Pydantic V2. In 2.13.5 we released experimental support for Pydantic V2, which made it technically co-installable via forced install. In this release we're enabling proper co-installation.

Release 2.13.6

This release includes:

📦 Default result storage block The new PREFECT_DEFAULT_RESULT_STORAGE_BLOCK setting allows users to set a default storage block on a work pool or via job variables for a deployment. It's now easier to swap result storage locations by updating the environment in the UI or your prefect.yaml file, eliminating the need to alter your flow source code.

🧪 Experimental enhanced cancellation We're enhancing the reliability of flow run cancellation, which you can try out by enabling the PREFECT_EXPERIMENTAL_ENABLE_ENHANCED_CANCELLATION feature. When enabled, you can cancel flow runs where cancellation can fail, such as when your worker is offline.

See the release notes for details!

Changelog

Sourced from prefect's changelog.

Prefect Release Notes

Release 2.13.6

Specify a default result storage block as a setting

Previously, specifying result storage blocks necessitated changes in the @flow or @task decorator. Now, the PREFECT_DEFAULT_RESULT_STORAGE_BLOCK setting allows users to set a default storage block on a work pool or via job variables for a deployment. For example, to set a default storage block for a deployment via prefect.yaml:

deployments:
- name: my-super-cool-deployment
  entrypoint: some_directory/some_file.py:my_flow
  schedule:
    cron: "0 20 * * 1-5"
  work_pool:
    name: ecs-pool
    job_variables:
      env:
        PREFECT_DEFAULT_RESULT_STORAGE_BLOCK: s3/my-s3-bucket-block-name

This enhancement enables easier swapping of result storages by just updating the environment in the UI or in your prefect.yaml, eliminating the need to alter your flow source code.

See the following pull request for details:

• PrefectHQ/prefect#10925

Experimental support for enhanced cancellation

We're introducing a new experimental feature that will enable more consistent and reliable cancellation of flow runs.

To enable enhanced cancellation, set the PREFECT_EXPERIMENTAL_ENABLE_ENHANCED_CANCELLATION setting on your worker or agents to True:

prefect config set PREFECT_EXPERIMENTAL_ENABLE_ENHANCED_CANCELLATION=True

When enabled, you can cancel flow runs where cancellation can fail, such as when your worker is offline. We will continue to develop enhanced cancellation to improve its reliability and performance. If you encounter any issues, please let us know in Slack or with a Github issue.

Note: If you are using the Kubernetes worker, you will need to update your prefect-kubernetes installation to 0.3.1. If you are using the Cloud Run or Vertex AI workers, you will need to update your prefect-gcp installation to 0.5.1.

See the following pull requests for details:

• PrefectHQ/prefect#10920
• PrefectHQ/prefect#10944

Enhancements

• Add link to Prefect Cloud information in the Prefect UI — PrefectHQ/prefect#10909

Fixes

• Avoid prefect deploy prompt for remote storage if a global pull step is already defined - PrefectHQ/prefect#10941

Documentation

... (truncated)

Commits

• 70f2d40 Docs: Update typo for 2.13.5-2.13.6 diff (#10950)
• d300750 Removes pin locking pydantic <2 (#10946)
• 8996e4a Release 2.13.6 (#10942)
• e30b5f0 Add documentation for experimental enhanced cancellation (#10944)
• d59788d prefect deploy: don't prompt remote storage if global pull step (#10941)
• 9f2ac9c add setting for default results storage block (#10925)
• 761a600 Add experimental enhanced cancellation (#10920)
• 474a7b6 mark test_process_kill_no_matching_pid as flaky (#10940)
• af98097 Update CSS for docs (#10913)
• 939f3bc docs: fix typo in logs guide (#10936)
• 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)