fix(print-platform): update dependency prefect to v2.10.21 #9790
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.10.20
->2.10.21
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
PrefectHQ/prefect (prefect)
v2.10.21
Compare Source
The Prefect Dashboard - your heads up display
The response to the experimental Prefect dashboard was so enthusiastic that we've made it generally availible as the default landing page in the Prefect UI. The dashboard provides an overview of all Prefect activity, surfaces the urgent information, and provides the context to understand that information. With the dashboard, you can:
Deploy deployments prefixed by flow name during
prefect deploy
You can now specify the deployment to be executed by prefixing the deployment name with the flow name.
For example, the following command creates a deployment with the name
my-deployment
for a flow with the namemy-flow
:This is especially useful when you have several flows with deployments that have the same name.
For implementation details, see the following pull request:
Use environment variables in deployment steps
Prefect now supports the usage of environment variables in deployment steps, allowing you to access environment variables during the
pull
action at runtime or during thebuild
andpush
actions when runningprefect deploy
. Particularly useful for CI/CD builds, this makes Prefect deployments more versatile.For example, you can now use the following syntax to set an image tag of a Dockerized build by loading an environment variable during the
build
action:User can also use environment variables inside of steps.
For example:
For implementation details, see the following pull request:
Use
prefect deploy
with multiple deployments with the same nameWhen there are multiple deployments with the same name, the
prefect deploy
command now prompts you to choose which one to deploy:For example, if you have the following
prefect.yaml
:running
prefect deploy -n default
will now prompt you to choose which flow to create a deployment for:For implementation details, see the following pull request:
Enhancements
SendgridEmail
notification block — https://github.com/PrefectHQ/prefect/pull/10118prefect deploy
nonexistent entrypointValueError
- https://github.com/PrefectHQ/prefect/pull/10210prefect deploy
table display - https://github.com/PrefectHQ/prefect/pull/10209prefect.runtime.flow_run.parent_flow_run_id
andprefect.runtime.flow_run.parent_deployment_id
- https://github.com/PrefectHQ/prefect/pull/10204Fixes
Documentation
mkdocs.yml
— https://github.com/PrefectHQ/prefect/pull/10187prefect profile get
- https://github.com/PrefectHQ/prefect/pull/10214Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.