|
1 | 1 | # Prefect Release Notes |
2 | 2 |
|
| 3 | +## Release 2.13.6 |
| 4 | + |
| 5 | +### Specify a default result storage block as a setting |
| 6 | + |
| 7 | +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`: |
| 8 | + |
| 9 | +```yaml |
| 10 | +deployments: |
| 11 | +- name: my-super-cool-deployment |
| 12 | + entrypoint: some_directory/some_file.py:my_flow |
| 13 | + schedule: |
| 14 | + cron: "0 20 * * 1-5" |
| 15 | + work_pool: |
| 16 | + name: ecs-pool |
| 17 | + job_variables: |
| 18 | + env: |
| 19 | + PREFECT_DEFAULT_RESULT_STORAGE_BLOCK: s3/my-s3-bucket-block-name |
| 20 | +``` |
| 21 | +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. |
| 22 | + |
| 23 | +See the following pull request for details: |
| 24 | +- https://github.com/PrefectHQ/prefect/pull/10925 |
| 25 | + |
| 26 | +### Experimental support for enhanced cancellation |
| 27 | + |
| 28 | +We're introducing a new experimental feature that will enable more consistent and reliable cancellation of flow runs. |
| 29 | + |
| 30 | +To enable enhanced cancellation, set the `PREFECT_EXPERIMENTAL_ENABLE_ENHANCED_CANCELLATION` setting on your worker or agents to `True`: |
| 31 | + |
| 32 | +```bash |
| 33 | +prefect config set PREFECT_EXPERIMENTAL_ENABLE_ENHANCED_CANCELLATION=True |
| 34 | +``` |
| 35 | + |
| 36 | +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. |
| 37 | + |
| 38 | +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`. |
| 39 | + |
| 40 | +See the following pull requests for details: |
| 41 | +- https://github.com/PrefectHQ/prefect/pull/10920 |
| 42 | +- https://github.com/PrefectHQ/prefect/pull/10944 |
| 43 | + |
| 44 | +### Enhancements |
| 45 | +- Add link to Prefect Cloud information in the Prefect UI — https://github.com/PrefectHQ/prefect/pull/10909 |
| 46 | + |
| 47 | +### Fixes |
| 48 | +- Avoid `prefect deploy` prompt for remote storage if a global pull step is already defined - https://github.com/PrefectHQ/prefect/pull/10941 |
| 49 | + |
| 50 | +### Documentation |
| 51 | +- Add a guide for using the Prefect client — https://github.com/PrefectHQ/prefect/pull/10924 |
| 52 | +- Remove icons from side navigation for improved readability — https://github.com/PrefectHQ/prefect/pull/10908 |
| 53 | +- Update deployments tutorial for consistent styling — https://github.com/PrefectHQ/prefect/pull/10911 |
| 54 | +- Fix typo in CLI command in deployments tutorial — https://github.com/PrefectHQ/prefect/pull/10937 |
| 55 | +- Fix typo in logging guide — https://github.com/PrefectHQ/prefect/pull/10936 |
| 56 | +- Update documentation styling — https://github.com/PrefectHQ/prefect/pull/10913 |
| 57 | + |
| 58 | +### Contributors |
| 59 | +* @Sun-of-a-beach made their first contribution in https://github.com/PrefectHQ/prefect/pull/10937 |
| 60 | +- @manaw |
| 61 | + |
| 62 | +**All changes**: https://github.com/PrefectHQ/prefect/compare/2.13.5...3.13.6 |
| 63 | + |
3 | 64 | ## Release 2.13.5 |
4 | 65 |
|
5 | 66 | ### Load and serve remotely stored flows |
|
0 commit comments