fix(greet): update dependency prefect to v2.13.0 #10968
Merged
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.12.1
->2.13.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
PrefectHQ/prefect (prefect)
v2.13.0
Compare Source
Introducing global concurrency limits
Control task execution and system stability with Prefect's new global concurrency and rate limits.
Concurrency Limits: Manage task execution efficiently, controlling how many tasks can run simultaneously. Ideal for optimizing resource usage and customizing task execution.
Rate Limits: Ensure system stability by governing the frequency of requests or operations. Perfect for preventing overuse, ensuring fairness, and handling errors gracefully.
Choose concurrency limits for resource optimization and task management, and opt for rate limits to maintain system stability and fair access to services. To begin using global concurrency limits check out our guide.
See the following pull request for details:
Introducing work pool and worker status
Work pools and workers are critical components of Prefect's distributed execution model. To help you monitor and manage your work pools and workers, we've added status indicators to the Prefect UI.
Work pools can now have one of three statuses:
Ready
- at least one online worker is polling the work pool and the work pool is ready to accept work.Not Ready
- no online workers are polling the work pool and indicates that action needs to be taken to allow the work pool to accept work.Paused
- the work pool is paused and work will not be executed until it is unpaused.Workers can now have one of two statuses:
Online
- the worker is polling the work pool and is ready to accept work.Offline
- the worker is not polling the work pool and is not ready to accept work. Indicates that the process running the worker has stopped or crashed.With the introduction of work pool and worker status, we are deprecating work queue health. Work queue health indicators will be removed in a future release.
See the documentation on work pool status and worker status for more information.
See the following pull request for details:
Removing deprecated Orion references
Six months ago, we deprecated references to
orion
in our codebase. In this release, we're removing those references. If you still have references toORION
in your profile, runprefect config validate
to automatically convert all of the settings in your current profile to the new names!For example:
Below is a full guide to the changes:
Settings renamed:
Changes:
See the following pull request for details:
orion
references — https://github.com/PrefectHQ/prefect/pull/10642Fixes
prefect server start
on Windows - https://github.com/PrefectHQ/prefect/pull/10547Documentation
--no-prompt
andPREFECT_CLI_PROMPT
to deployment documentation — https://github.com/PrefectHQ/prefect/pull/10600All changes: PrefectHQ/prefect@2.12.1...2.13.0
Configuration
📅 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.